Triple
T22095523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braintree Split |
E546016
|
entity |
| Predicate | roadDesign |
P1777
|
FINISHED |
| Object | complex multi-level interchange |
—
|
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: complex multi-level interchange | Statement: [Braintree Split, roadDesign, complex multi-level interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDesign Context triple: [Braintree Split, roadDesign, complex multi-level interchange]
-
A.
roadDesignApproach
Indicates the method or strategy used to plan, configure, or engineer the design of a road or roadway system.
-
B.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
C.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
D.
trackDesigner
Indicates that one entity is the designer or creator responsible for the layout or structure of a track associated with another entity.
-
E.
trailDesignation
Indicates that a particular label, name, or classification has been assigned to a trail to identify its route, type, or official status.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e82c1481908701f255b834f192 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.