Triple
T31589789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BxM1 |
E806058
|
entity |
| Predicate | routeNumberPrefix |
P66494
|
FINISHED |
| Object | BxM |
—
|
NE NERFINISHED |
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: BxM | Statement: [BxM1, routeNumberPrefix, BxM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNumberPrefix Context triple: [BxM1, routeNumberPrefix, BxM]
-
A.
roadNumberPrefix
chosen
Indicates that one entity is a prefix portion of the road number or designation used by the other entity.
-
B.
routeNumberPrecededBy
Indicates that one route number comes immediately before another route number in an ordered sequence.
-
C.
routeNumberFormat
Indicates how the identifying number or code for a route is structured or formatted.
-
D.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
E.
routeNumberSignedAs
Indicates that a route is officially signed or labeled with a particular route number on physical or digital signage.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a82eb2848190b5329618001a90fd |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:27 p.m.