Triple
T8462038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sluice Weir Lock |
E200063
|
entity |
| Predicate | enablesPassageOf |
P3947
|
FINISHED |
| Object | boats |
—
|
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: boats | Statement: [Sluice Weir Lock, enablesPassageOf, boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesPassageOf Context triple: [Sluice Weir Lock, enablesPassageOf, boats]
-
A.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
B.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
D.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
E.
passesThroughFacility
chosen
Indicates that something (such as a person, object, or shipment) moves through or is routed via a particular facility as part of its path or process.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a251f08190840a7fc31ff528b5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.