Triple
T20940082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broye Canal |
E515694
|
entity |
| Predicate | hasEngineeringType |
P77595
|
FINISHED |
| Object | regulation canal |
—
|
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: regulation canal | Statement: [Broye Canal, hasEngineeringType, regulation canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringType Context triple: [Broye Canal, hasEngineeringType, regulation canal]
-
A.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
-
B.
hasEngineeringFunction
Indicates that an entity possesses or performs a specific engineering-related role, purpose, or operational function.
-
C.
typeOfEngineering
chosen
Indicates that one entity is a specific branch, category, or kind of engineering to which the other entity belongs.
-
D.
isEngineeringStructureOf
Indicates that one entity serves as an engineering structure that is functionally or structurally associated with, or part of, another entity.
-
E.
hasEngineeringSignificance
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f954e44481909098a0b23a687d5e |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.