Triple
T4347858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Power Authority in 2017 |
E97947
|
entity |
| Predicate | publicOwner |
P347
|
FINISHED |
| Object | people of the State of New York |
—
|
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: people of the State of New York | Statement: [New York Power Authority in 2017, publicOwner, people of the State of New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicOwner Context triple: [New York Power Authority in 2017, publicOwner, people of the State of New York]
-
A.
primaryOwner
Indicates that one entity is the main or principal owner of another entity, having the highest level of ownership or control among all possible owners.
-
B.
partOwner
Indicates that one entity holds a partial or shared ownership stake in another entity.
-
C.
standardOwner
Indicates that one entity is the primary or default owner of another entity according to a defined standard or convention.
-
D.
complexOwner
Indicates that one entity possesses or holds ownership over a complex object, structure, or multi-part asset.
-
E.
ownedBy
chosen
Indicates that one entity possesses legal or rightful ownership of another entity.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a5559c819081608b0aaf6a0e66 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.