Triple
T17672908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeelandbrug |
E440570
|
entity |
| Predicate | navigationSpanType |
P25384
|
FINISHED |
| Object | bascule section |
—
|
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: bascule section | Statement: [Zeelandbrug, navigationSpanType, bascule section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationSpanType Context triple: [Zeelandbrug, navigationSpanType, bascule section]
-
A.
navigationSpanLength
Indicates the distance or extent covered by a navigation segment or span within a route or path.
-
B.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
-
C.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
D.
spanType
chosen
Indicates the specific category or kind of span that characterizes the relationship or action between entities.
-
E.
leafSpan
Indicates the extent or range covered by a leaf, such as its length, width, or overall spread.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6aa64081908c9a82128a5a9024 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.