Triple
T35147768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strijpen |
E1014890
|
entity |
| Predicate | hasLocalRoadType |
P74765
|
FINISHED |
| Object | municipal roads |
—
|
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: municipal roads | Statement: [Strijpen, hasLocalRoadType, municipal roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalRoadType Context triple: [Strijpen, hasLocalRoadType, municipal roads]
-
A.
hasLocalRoad
Indicates that there exists a local road connection or association between the related entities.
-
B.
hasRoadNetworkType
chosen
Indicates the type or classification of road network associated with or present in an entity.
-
C.
appliesToRoadType
Indicates that a rule, condition, or attribute is specifically relevant or valid for a particular type or category of road.
-
D.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
E.
hasRoadClass
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:02 p.m.