Triple
T7732445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 152 |
E175292
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 152
SR 152 is a state highway in Maine that runs generally north–south, connecting several rural communities and serving as a regional connector route.
|
E684052
|
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 152 | Statement: [Maine State Route 152, abbreviation, SR 152]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 152 Context triple: [Maine State Route 152, abbreviation, SR 152]
-
A.
SR 15
SR 15 is a state highway in Maine that runs through the city of Brewer and connects several communities in the region.
-
B.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
C.
SR 188
SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
-
D.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
E.
SR 155
SR 155 is a state highway in Alabama that serves as a connector route within the state's road network.
- 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 152 Triple: [Maine State Route 152, abbreviation, SR 152]
Generated description
SR 152 is a state highway in Maine that runs generally north–south, connecting several rural communities and serving as a regional connector route.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 152 Target entity description: SR 152 is a state highway in Maine that runs generally north–south, connecting several rural communities and serving as a regional connector route.
-
A.
SR 15
SR 15 is a state highway in Maine that runs through the city of Brewer and connects several communities in the region.
-
B.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
C.
SR 188
SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
-
D.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
E.
SR 155
SR 155 is a state highway in Alabama that serves as a connector route within the state's road network.
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7033863d881909451a4f9675021a3 |
completed | March 27, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b531a7f481908e4ff7f15b851070 |
completed | March 29, 2026, 5:14 a.m. |
| NEDg | Description generation | batch_69c8b5fbda848190b09172740371fd47 |
completed | March 29, 2026, 5:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c8b675ddb0819085d79dbba560d08f |
completed | March 29, 2026, 5:19 a.m. |
Created at: March 27, 2026, 4:06 p.m.