Triple
T17163663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztlan |
E416548
|
entity |
| Predicate | locationHypothesis |
P28981
|
FINISHED |
| Object | north or northwest of the Valley of Mexico |
—
|
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: north or northwest of the Valley of Mexico | Statement: [Aztlan, locationHypothesis, north or northwest of the Valley of Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationHypothesis Context triple: [Aztlan, locationHypothesis, north or northwest of the Valley of Mexico]
-
A.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
B.
possibleLocation
chosen
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
C.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
locationDescription
Indicates a textual description that specifies or characterizes the location of an 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f913c84481908bb5da8bcc6a2e62 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.