Triple
T26789527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oich Bridge |
E670475
|
entity |
| Predicate | allowsCanalTraffic |
P169924
|
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: [Oich Bridge, allowsCanalTraffic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsCanalTraffic Context triple: [Oich Bridge, allowsCanalTraffic, true]
-
A.
containsCanal
Indicates that one geographical or spatial entity has a canal located within its boundaries or interior.
-
B.
hasCanalParallel
Indicates that one canal runs parallel to another canal without intersecting it.
-
C.
hasCanalDirection
Indicates that a canal has a specific directional orientation or flow direction relative to a reference.
-
D.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
-
E.
hasCanalCrossing
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 4:15 a.m.