Triple

T17983999
Position Surface form Disambiguated ID Type / Status
Subject Priest Rapids Dam E430176 entity
Predicate isPublicUtilityProject P130004 FINISHED
Object yes 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: yes | Statement: [Priest Rapids Dam, isPublicUtilityProject, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPublicUtilityProject
Context triple: [Priest Rapids Dam, isPublicUtilityProject, yes]
  • A. isPublicInfrastructure
    Indicates that something is part of publicly accessible, collectively used facilities or systems typically provided or regulated by government for common use.
  • B. isPublicParticipationProject
    Indicates that an activity or initiative is a project designed for and involving participation by the general public.
  • C. isPublicBuilding
    Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
  • D. isPartOfUrbanProject
    Indicates that something belongs to, is included within, or constitutes a component of a broader urban development project.
  • E. isNonProfitProjectOf
    Indicates that a project operates on a non-profit basis and is initiated, owned, or managed by the referenced entity.
  • 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_69d8b90364248190a37381adea932f42 completed April 10, 2026, 8:46 a.m.
NER Named-entity recognition batch_69e4b2992fe481908c0d2757b4de5bad completed April 19, 2026, 10:46 a.m.
PD Predicate disambiguation batch_69e3f8fa62688190a5d5c361ab896256 completed April 18, 2026, 9:34 p.m.
PDg Predicate description generation batch_69e42d8d68288190a05dc5d7803cf823 completed April 19, 2026, 1:19 a.m.
Created at: April 10, 2026, 10:23 a.m.