Triple

T36414717
Position Surface form Disambiguated ID Type / Status
Subject Lee Conservancy E896973 entity
Predicate historicallyOverseenBy P19592 FINISHED
Object navigation authorities 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: navigation authorities | Statement: [Lee Conservancy, historicallyOverseenBy, navigation authorities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyOverseenBy
Context triple: [Lee Conservancy, historicallyOverseenBy, navigation authorities]
  • A. historicallyControlledBy
    Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
  • B. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • C. historicallyResponsibleFor
    Indicates that an entity bears responsibility, typically recognized in historical analysis, for causing, contributing to, or being accountable for a past event, condition, or outcome.
  • D. roleHistoricallyAssociatedWith
    Indicates that one role, position, or function has been historically linked or commonly associated with another entity, role, or context over time.
  • E. historicallyServedBy chosen
    Indicates that an entity was provided with services or support by another entity during a past period of time.
  • 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_69f76e54ce408190849acc3f7758937c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a0127c36dc08190b07765756b3d0e1b completed May 11, 2026, 12:50 a.m.
PD Predicate disambiguation batch_6a0125ef57208190be5b5e761fcae981 completed May 11, 2026, 12:42 a.m.
Created at: May 3, 2026, 4:10 p.m.