Triple

T13440217
Position Surface form Disambiguated ID Type / Status
Subject Beaver E320339 entity
Predicate usesStructureFor P35482 FINISHED
Object dams for water level control 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: dams for water level control | Statement: [Beaver, usesStructureFor, dams for water level control]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesStructureFor
Context triple: [Beaver, usesStructureFor, dams for water level control]
  • A. usedStructure chosen
    Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
  • B. usedInStructure
    Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
  • C. reusesStructureOf
    Indicates that one entity adopts or incorporates the structural design or organization of another entity.
  • D. supportsStructure
    Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
  • E. convertedStructureUse
    Indicates that an entity’s original structural use has been changed to a different use or function.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaee704ac8190b4c7f4e0d3a88494 completed April 12, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69d9a03926188190ab3948d1f5d3941f completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:40 p.m.