Triple

T22350709
Position Surface form Disambiguated ID Type / Status
Subject Yamakuni River E552518 entity
Predicate hasRelatedInfrastructure P137157 FINISHED
Object levees 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: levees | Statement: [Yamakuni River, hasRelatedInfrastructure, levees]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRelatedInfrastructure
Context triple: [Yamakuni River, hasRelatedInfrastructure, levees]
  • A. relatedInfrastructure
    Indicates that one piece of infrastructure is connected, associated, or functionally related to another infrastructure element.
  • B. infrastructureAssociatedWith
    Indicates a relationship where a piece of infrastructure is functionally or contextually connected to, supports, or is used by another entity.
  • C. hasInfrastructureAlong chosen
    Indicates that infrastructure is present or extends along the length or course of another entity (such as a route, boundary, or geographic feature).
  • D. hasInfrastructureType
    Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
  • E. hasAccessInfrastructure
    Indicates that an entity is equipped with or connected to the physical or technical infrastructure necessary to access a particular service, resource, or network.
  • 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_69e11e4a0ad08190a385b4d343cf6524 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1579be6d8819088fed70f54ff4e66 completed April 29, 2026, 12:58 a.m.
PD Predicate disambiguation batch_69e7300c20088190a59e5bf9e70384f3 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:43 p.m.