Triple
T35674410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaški |
E1030813
|
entity |
| Predicate | hasLocalRoadConnections |
P49867
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Plaški, hasLocalRoadConnections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalRoadConnections Context triple: [Plaški, hasLocalRoadConnections, true]
-
A.
hasLocalRoad
chosen
Indicates that there exists a local road connection or association between the related entities.
-
B.
hasRoadConnectionRegion
Indicates that there is a road-based transportation link connecting one region to another.
-
C.
hasNearbyInternationalRoad
Indicates that an entity is located close to an international road or highway that crosses national borders.
-
D.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
E.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 3, 2026, 4:05 p.m.