Triple
T28019867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M Track |
E707655
|
entity |
| Predicate | hasRoadbedMaterial |
P180138
|
FINISHED |
| Object | metal roadbed |
—
|
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: metal roadbed | Statement: [M Track, hasRoadbedMaterial, metal roadbed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadbedMaterial Context triple: [M Track, hasRoadbedMaterial, metal roadbed]
-
A.
hasEmbankmentMaterial
Indicates that an embankment is composed of, or constructed using, a specified material.
-
B.
streetMaterial
Indicates the material composition from which a street or road surface is made.
-
C.
hasSidewalkMaterial
Indicates that a sidewalk is composed of, or constructed using, a specified material.
-
D.
hasRoadCondition
Indicates that a specified road segment possesses or is characterized by a particular condition or state (e.g., quality, surface, or status).
-
E.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
- F. None of above. chosen
Provenance (4 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 27, 2026, 8:09 p.m.