Triple
T37398056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-125 |
E928911
|
entity |
| Predicate | hasRouteTypePrefix |
P138993
|
FINISHED |
| Object | M |
—
|
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: M | Statement: [M-125, hasRouteTypePrefix, M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteTypePrefix Context triple: [M-125, hasRouteTypePrefix, M]
-
A.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
B.
hasRoadTypePrefix
chosen
Indicates that a road-related identifier or name begins with a specific road type prefix (such as "Highway", "Route", or "Street").
-
C.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
D.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
E.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 3, 2026, 4:16 p.m.