Triple
T25455376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lock 21 |
E637899
|
entity |
| Predicate | isNumberedElementOf |
P22578
|
FINISHED |
| Object | Rideau Canal lock system |
—
|
NE NERFINISHED |
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: Rideau Canal lock system | Statement: [Lock 21, isNumberedElementOf, Rideau Canal lock system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedElementOf Context triple: [Lock 21, isNumberedElementOf, Rideau Canal lock system]
-
A.
isNumberedRelativeTo
Indicates that one entity’s numbering or ordinal position is defined or interpreted in relation to another entity.
-
B.
isNumbered
chosen
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
C.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
D.
isNumberedParallelTo
Indicates that one linear entity is parallel to another and has an assigned identifying number distinguishing it from other parallel entities.
-
E.
isNumberedWithinState
Indicates that an entity has an assigned number that is unique or valid only within the context or boundaries of a particular state.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f725e4d08190b0304e45a417193b |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:04 p.m.