Triple
T3500503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M25 |
E73953
|
entity |
| Predicate | hasJunctionNumberingTo |
P43890
|
FINISHED |
| Object | 31 |
—
|
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: 31 | Statement: [M25, hasJunctionNumberingTo, 31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJunctionNumberingTo Context triple: [M25, hasJunctionNumberingTo, 31]
-
A.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
-
B.
hasJunctionNumber
chosen
Indicates that a road, route, or similar pathway is assigned a specific junction or exit number.
-
C.
hasJunctionNumberingScheme
Indicates the specific system or method used to assign numbers to junctions within a network (such as roads or railways).
-
D.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
-
E.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd4eb308190b84e84261ceec229 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.