Triple
T12988256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico State Road 13 |
E321824
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object |
SR 13
SR 13 is a state highway in New Mexico that serves as a regional connector route across rural areas of the state.
|
E1020855
|
NE FINISHED |
How this triple was built (4 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: SR 13 | Statement: [New Mexico State Road 13, hasAbbreviation, SR 13]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 13 Context triple: [New Mexico State Road 13, hasAbbreviation, SR 13]
-
A.
SR 13
SR 13 is a north–south state highway in Ohio that runs between the city of Mansfield and the village of Huron, passing through several counties in the north-central part of the state.
-
B.
SR 130
SR 130 is a state highway in Maine that runs through Lincoln County, connecting inland communities to the Pemaquid Point area on the Atlantic coast.
-
C.
SR 138
SR 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
-
D.
SR 132
SR 132 is a state highway in Maine that connects several small communities and links with other major regional routes.
-
E.
SR 131
SR 131 is a state highway in Maine that runs through Knox and Waldo counties, connecting several coastal and inland communities.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SR 13 Triple: [New Mexico State Road 13, hasAbbreviation, SR 13]
Generated description
SR 13 is a state highway in New Mexico that serves as a regional connector route across rural areas of the state.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 13 Target entity description: SR 13 is a state highway in New Mexico that serves as a regional connector route across rural areas of the state.
-
A.
SR 13
SR 13 is a north–south state highway in Ohio that runs between the city of Mansfield and the village of Huron, passing through several counties in the north-central part of the state.
-
B.
SR 130
SR 130 is a state highway in Maine that runs through Lincoln County, connecting inland communities to the Pemaquid Point area on the Atlantic coast.
-
C.
SR 138
SR 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
-
D.
SR 132
SR 132 is a state highway in Maine that connects several small communities and links with other major regional routes.
-
E.
SR 131
SR 131 is a state highway in Maine that runs through Knox and Waldo counties, connecting several coastal and inland communities.
- F. None of above. chosen
Provenance (5 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e5f47ec8190b39107bc016f9824 |
completed | April 10, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5f4bedc81909b8dfa79a842e12d |
completed | May 3, 2026, 4:58 a.m. |
| NEDg | Description generation | batch_69f6da5695508190a96ca16a4e5c01ee |
completed | May 3, 2026, 5:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f6daeae96081908f6d9cda3ff7f961 |
completed | May 3, 2026, 5:19 a.m. |
Created at: April 9, 2026, 8:42 p.m.