Triple
T30953542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilbury Ferry |
E788609
|
entity |
| Predicate | providesPedestrianLink |
P132153
|
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: [Tilbury Ferry, providesPedestrianLink, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesPedestrianLink Context triple: [Tilbury Ferry, providesPedestrianLink, true]
-
A.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
B.
hasPedestrianOverpass
Indicates that there exists a pedestrian overpass connecting or spanning parts of the referenced location or infrastructure.
-
C.
isPedestrianGateway
Indicates that something serves as an access point or entrance specifically intended for use by pedestrians.
-
D.
pedestrianRestrictions
Indicates that there are specific rules or limitations governing where or how pedestrians may travel or access an area.
-
E.
isTransportationLinkBetween
chosen
Indicates that there exists a transportation connection (such as a road, rail, air, or sea route) linking the two 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 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: April 29, 2026, 8:53 p.m.