Triple
T4398312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humber Bridge |
E99547
|
entity |
| Predicate | hasPedestrianPath |
P18406
|
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: [Humber Bridge, hasPedestrianPath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianPath Context triple: [Humber Bridge, hasPedestrianPath, true]
-
A.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
B.
hasPedestrianArea
chosen
Indicates that a location or zone includes a designated area intended for pedestrian use only or primarily.
-
C.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
D.
hasPedestrianPhase
Indicates that a traffic signal includes a dedicated phase during which pedestrians are allowed to cross.
-
E.
hasPedestrianCharacter
Indicates that something possesses qualities, features, or behavior characteristic of pedestrians or pedestrian use.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352adce588190b9e6ed53458aa1e1 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:20 p.m.