Triple
T38185695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico State Road 371 |
E1005309
|
entity |
| Predicate | westernUSState |
P190268
|
FINISHED |
| Object | New Mexico |
—
|
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 Mexico | Statement: [New Mexico State Road 371, westernUSState, New Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernUSState Context triple: [New Mexico State Road 371, westernUSState, New Mexico]
-
A.
westernTerminusState
Indicates the state in which something (such as a route, line, or path) has its western endpoint or terminus.
-
B.
westernTerminusConnectsTo
Indicates that the western endpoint or terminus of one route, line, or path is directly connected to another specified route, line, or location.
-
C.
westernSideState
Indicates that a state is located on or corresponds to the western side of a specified geographic or political region.
-
D.
USStateRegion
Indicates that a U.S. state is located within or belongs to a particular geographic region of the United States.
-
E.
westernTerminusCountry
Indicates the country in which the westernmost endpoint of something (such as a route, line, or feature) is located.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:29 p.m.