Triple
T15946377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 208 |
E386693
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
ME 208
ME 208 is a short state highway in Maine that serves as a local connector route within the state’s road network.
|
E1184251
|
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: ME 208 | Statement: [Maine State Route 208, abbreviation, ME 208]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ME 208 Context triple: [Maine State Route 208, abbreviation, ME 208]
-
A.
ME 203
ME 203 is a state highway in Maine that serves as a short connector route between local communities.
-
B.
ME 207
ME 207 is a state highway in Maine that serves as a local connector route within the state's road network.
-
C.
ME 205
ME 205 is a state highway in Maine that serves as a local connector route within the state's road network.
-
D.
ME 185
ME 185 is a state highway in Maine that serves as a local connector route, typically linking small communities and other regional roads.
-
E.
ME 183
ME 183 is a short state highway in Maine that serves as a local connector route in Hancock County.
- 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: ME 208 Triple: [Maine State Route 208, abbreviation, ME 208]
Generated description
ME 208 is a short state highway in Maine that serves as a local connector route within the state’s road network.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ME 208 Target entity description: ME 208 is a short state highway in Maine that serves as a local connector route within the state’s road network.
-
A.
ME 203
ME 203 is a state highway in Maine that serves as a short connector route between local communities.
-
B.
ME 207
ME 207 is a state highway in Maine that serves as a local connector route within the state's road network.
-
C.
ME 205
ME 205 is a state highway in Maine that serves as a local connector route within the state's road network.
-
D.
ME 185
ME 185 is a state highway in Maine that serves as a local connector route, typically linking small communities and other regional roads.
-
E.
ME 183
ME 183 is a short state highway in Maine that serves as a local connector route in Hancock County.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156d1a4c08190afc325491ba38870 |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5c0c8a481908aa7a40bca15e38e |
completed | May 9, 2026, 10:31 p.m. |
| NEDg | Description generation | batch_69ffb6d3bc6c81909e4bbedeea557615 |
completed | May 9, 2026, 10:36 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ffb7364cf88190b0930af7768dc429 |
completed | May 9, 2026, 10:37 p.m. |
Created at: April 10, 2026, 4:53 a.m.