Triple
T28883967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mixtec religion |
E732500
|
entity |
| Predicate | usesWritingSource |
P153734
|
FINISHED |
| Object | Mixtec codices |
—
|
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: Mixtec codices | Statement: [Mixtec religion, usesWritingSource, Mixtec codices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWritingSource Context triple: [Mixtec religion, usesWritingSource, Mixtec codices]
-
A.
usesWriting
Indicates that one entity employs or applies a particular writing system, script, or written form for communication or representation.
-
B.
usedToWrite
Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
-
C.
hasWriterSource
Indicates that the writer of one entity is derived from, based on, or sourced from another entity.
-
D.
usesWritingCenter
Indicates that an entity makes use of the services or resources provided by a writing center.
-
E.
hasWritingAssociated
chosen
Indicates that there is a piece of writing (such as a text, document, or inscription) linked or connected to the given 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a6fc5088190af152ba43c0b91e5 |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:48 a.m.