Triple
T8910410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheppey Crossing |
E212166
|
entity |
| Predicate | navigationClearance |
P86325
|
FINISHED |
| Object | higher than Kingsferry Bridge |
—
|
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: higher than Kingsferry Bridge | Statement: [Sheppey Crossing, navigationClearance, higher than Kingsferry Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationClearance Context triple: [Sheppey Crossing, navigationClearance, higher than Kingsferry Bridge]
-
A.
navigationClearanceType
Indicates the specific type or category of clearance granted for a navigation-related operation or movement.
-
B.
hasNavigationClearance
Indicates that an entity has been granted authorization to navigate through a specified area or along a particular route.
-
C.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
-
D.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
E.
flightRules
Indicates the regulatory or procedural rules that govern how a flight must be conducted or operated.
- F. None of above. chosen
Provenance (4 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65227d008190b13ba162d0b3c9d1 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc604965c48190bbb6db0ae8108e67 |
completed | April 1, 2026, 12:01 a.m. |
Created at: March 30, 2026, 6:55 p.m.