Triple
T22900196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilimanuk Port |
E568288
|
entity |
| Predicate | hasVehicleLanes |
P2128
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gilimanuk Port, hasVehicleLanes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVehicleLanes Context triple: [Gilimanuk Port, hasVehicleLanes, yes]
-
A.
hasLanes
chosen
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
B.
laneCount
Indicates the number of parallel lanes associated with a given road or roadway segment.
-
C.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
D.
hasTrackLanes
Indicates that an entity (such as a road or track) includes one or more designated lanes for vehicle or train movement.
-
E.
hasLaneSeparation
Indicates that there is a physical or marked separation between traffic lanes.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801626488190b7e8ce3301667987 |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:41 p.m.