Triple
T31922729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B2157 |
E815014
|
entity |
| Predicate | hasRoadTypeCode |
P138993
|
FINISHED |
| Object | B |
—
|
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: B | Statement: [B2157, hasRoadTypeCode, B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadTypeCode Context triple: [B2157, hasRoadTypeCode, B]
-
A.
hasRoadClass
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
-
B.
hasRoadCode
Indicates that an entity is associated with a specific road identification code used for classification or reference.
-
C.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
D.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
E.
hasRoadTypePrefix
chosen
Indicates that a road-related identifier or name begins with a specific road type prefix (such as "Highway", "Route", or "Street").
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 12:03 a.m.