Triple
T4347886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Power Authority in 2017 |
E97947
|
entity |
| Predicate | usesRevenueFor |
P9389
|
FINISHED |
| Object | operation of power assets |
—
|
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: operation of power assets | Statement: [New York Power Authority in 2017, usesRevenueFor, operation of power assets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRevenueFor Context triple: [New York Power Authority in 2017, usesRevenueFor, operation of power assets]
-
A.
revenueUse
chosen
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
-
B.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
C.
revenueSources
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
D.
revenueLevel
Indicates the relative amount or tier of revenue associated with an entity or activity.
-
E.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
- 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.