Triple
T16890106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Island Dam |
E424145
|
entity |
| Predicate | isOwnedByPublicUtility |
P114322
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rock Island Dam, isOwnedByPublicUtility, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOwnedByPublicUtility Context triple: [Rock Island Dam, isOwnedByPublicUtility, true]
-
A.
municipalUtilityAssetOf
Indicates that a given asset is owned, managed, or operated by a municipal utility of the referenced municipality.
-
B.
isPublicInfrastructure
Indicates that something is part of publicly accessible, collectively used facilities or systems typically provided or regulated by government for common use.
-
C.
electricityProviderType
Indicates the specific category or kind of electricity provider associated with an entity.
-
D.
publiclyOperatedBy
chosen
Indicates that an entity is managed or run by a public or government organization.
-
E.
electrificationUsedByOtherOperator
Indicates that the type of railway electrification in question is utilized by an operator other than the primary or referenced operator.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc3b5188190ac713b4d4166e961 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.