Triple

T27498804
Position Surface form Disambiguated ID Type / Status
Subject Kissimmee River E694091 entity
Predicate channelizationProject P162453 FINISHED
Object C-38 Canal 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: C-38 Canal | Statement: [Kissimmee River, channelizationProject, C-38 Canal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: channelizationProject
Context triple: [Kissimmee River, channelizationProject, C-38 Canal]
  • A. channelLining
    Indicates the presence or application of a protective or functional lining along the interior surface of a channel or conduit.
  • B. channels
    Indicates that one entity serves as a medium, route, or conduit through which another entity is directed, transmitted, or delivered.
  • C. channelAccess
    Indicates that one entity has permission or ability to use, view, or interact with a particular communication channel or medium associated with another entity.
  • D. channelSpecialization
    Indicates that one channel is a more specialized or focused version of another, typically refining or narrowing the scope of the broader channel.
  • E. canChannel
    Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
  • 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_69ef538370888190b1ddf53bb4831188 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62ec0c9888190a7f0de2aa4d1d0b1 completed May 2, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f623aaf40081909f947431424a1d55 completed May 2, 2026, 4:17 p.m.
PDg Predicate description generation batch_69f624c006788190a2f4d5015c96463f completed May 2, 2026, 4:22 p.m.
Created at: April 27, 2026, 1:10 p.m.