Triple
T25267887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Chimalpopoca |
E633480
|
entity |
| Predicate | originallyCreatedIn |
P13656
|
FINISHED |
| Object | New Spain |
—
|
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: New Spain | Statement: [Codex Chimalpopoca, originallyCreatedIn, New Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyCreatedIn Context triple: [Codex Chimalpopoca, originallyCreatedIn, New Spain]
-
A.
originallyProducedIn
Indicates that something was first created, manufactured, or brought into existence in a particular place or location.
-
B.
originallyIn
chosen
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
C.
originallyProducedAs
Indicates that one entity was first created, released, or manufactured in the form of another specified entity or format.
-
D.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
E.
originallyBuilt
Indicates that one entity was the first or initial builder or constructor of 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 21, 2026, 1:16 p.m.