Triple
T25325186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carillon dam |
E634991
|
entity |
| Predicate | hasLockLift |
P166574
|
FINISHED |
| Object | about 20 m |
—
|
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: about 20 m | Statement: [Carillon dam, hasLockLift, about 20 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockLift Context triple: [Carillon dam, hasLockLift, about 20 m]
-
A.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
B.
hasLiftType
Indicates the specific type or category of lift associated with an entity.
-
C.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
-
D.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
E.
hasLockNumber
Indicates that an entity is associated with a specific lock identified by a number.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 21, 2026, 1:30 p.m.