Triple
T13180681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 128 (Maine) |
E313713
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | ME 128 |
E803076
|
NE 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: ME 128 | Statement: [State Route 128 (Maine), abbreviation, ME 128]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ME 128 Context triple: [State Route 128 (Maine), abbreviation, ME 128]
-
A.
ME 128
chosen
ME 128 is a state highway in Maine that serves as a regional connector route between local communities.
-
B.
ME 168
ME 168 is a state highway in Maine that serves as a short connector route between local communities in the region.
-
C.
ME 148
ME 148 is a state highway in Maine that serves as a regional connector route between local communities.
-
D.
ME 158
ME 158 is a short state highway in Maine that serves as a connector route within the state's regional road network.
-
E.
ME 132
ME 132 is a state highway in Maine that serves as a regional connector route between local communities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c490ed081908ea54edb25c3de90 |
completed | April 10, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5ee66188190afb75a598a2f8211 |
completed | May 3, 2026, 7:14 a.m. |
Created at: April 9, 2026, 9:14 p.m.