Triple
T741797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenochtitlan founding legend |
E15258
|
entity |
| Predicate | prophecyLocation |
P9185
|
FINISHED |
| Object | island in Lake Texcoco |
—
|
LITERAL FINISHED |
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: island in Lake Texcoco | Statement: [Tenochtitlan founding legend, prophecyLocation, island in Lake Texcoco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prophecyLocation Context triple: [Tenochtitlan founding legend, prophecyLocation, island in Lake Texcoco]
-
A.
revelationPlace
chosen
Indicates the place or location where a revelation, disclosure, or revealing event occurs.
-
B.
followsProphet
Indicates that one entity accepts the guidance or teachings of, and adheres to the leadership or example set by, a prophet.
-
C.
firstRevelationPlace
Indicates the location where something (typically a text, message, or revelation) was first revealed or disclosed.
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
positionAmongMajorProphets
Indicates the relative ordering or placement of an item within the group traditionally known as the Major Prophets.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60e286c81908787a41cf9b9f150 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.