Triple
T34490129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dexter, New Mexico |
E885443
|
entity |
| Predicate | directionFromRoswell |
P195247
|
FINISHED |
| Object | southeast |
—
|
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: southeast | Statement: [Dexter, New Mexico, directionFromRoswell, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromRoswell Context triple: [Dexter, New Mexico, directionFromRoswell, southeast]
-
A.
directionFromPhoenix
Indicates the cardinal or relative compass direction of an entity as measured from Phoenix.
-
B.
directionFromDodgeCity
Indicates the spatial direction or bearing of one entity as measured from the location of Dodge City.
-
C.
directionRelativeToEmeraldCity
Indicates the compass direction or positional bearing of one place or object relative to the location of Emerald City.
-
D.
directionFromFortWorth
Indicates the compass direction in which one entity is located relative to Fort Worth.
-
E.
directionFromAtlanta
Indicates the cardinal or relative compass direction in which one entity is located from Atlanta.
- F. None of above. chosen
Provenance (4 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: May 1, 2026, 2:01 a.m.