Triple
T26712871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mixteca region |
E673468
|
entity |
| Predicate | producedCodex |
P74478
|
FINISHED |
| Object | Codex Nuttall |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Codex Nuttall | Statement: [Mixteca region, producedCodex, Codex Nuttall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedCodex Context triple: [Mixteca region, producedCodex, Codex Nuttall]
-
A.
codicesFunctionAs
Indicates that certain codices serve a particular role, purpose, or function in relation to something else.
-
B.
sisterCodex
Indicates a sibling relationship where one codex or text is considered a sister counterpart to another, typically implying close similarity, shared origin, or parallel status.
-
C.
producedAs
chosen
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
D.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
E.
codifiedFor
Indicates that something has been formally organized, standardized, or written down specifically for use by or application to another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 3:36 a.m.