Triple
T1375600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam ferry network |
E29213
|
entity |
| Predicate | allowsVehicleType |
P1776
|
FINISHED |
| Object | pedestrians |
—
|
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: pedestrians | Statement: [Amsterdam ferry network, allowsVehicleType, pedestrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsVehicleType Context triple: [Amsterdam ferry network, allowsVehicleType, pedestrians]
-
A.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
B.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
hasPrimaryVehicularAccessTo
Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
-
D.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
-
E.
associatedVehicleWeightClass
Indicates the weight classification category that is linked or assigned to a particular vehicle.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2f7aeb08190b52ef1058c18327e |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.