Triple
T9414969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 127 |
E226994
|
entity |
| Predicate | hasRouteTypeAbbreviation |
P8075
|
FINISHED |
| Object | SR |
—
|
LITERAL 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: SR | Statement: [Maine State Route 127, hasRouteTypeAbbreviation, SR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteTypeAbbreviation Context triple: [Maine State Route 127, hasRouteTypeAbbreviation, SR]
-
A.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
B.
hasAbbreviationPattern
Indicates that there is a systematic abbreviation relationship between two strings, where one follows a recognizable pattern derived from the other.
-
C.
hasNameAbbreviation
chosen
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
D.
isAbbreviation
Indicates that one term is a shortened or abbreviated form of another term.
-
E.
typeOfAbbreviation
Indicates that one term is an abbreviation of a specific type or category (e.g., acronym, initialism) of another expression.
- F. None of above.
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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c7bd648190b17f082883c98239 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.