Triple
T13195222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Theater |
E314093
|
entity |
| Predicate | fundingSourceForRenaming |
P25106
|
FINISHED |
| Object | donation by David H. Koch |
—
|
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: donation by David H. Koch | Statement: [New York State Theater, fundingSourceForRenaming, donation by David H. Koch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingSourceForRenaming Context triple: [New York State Theater, fundingSourceForRenaming, donation by David H. Koch]
-
A.
renamingSponsor
chosen
Indicates that one entity serves as the sponsor responsible for the renaming of another entity.
-
B.
renamingAuthority
Indicates that the subject has the authority or power to change the name or designation of the object.
-
C.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
D.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
E.
renamingSupportedBy
Indicates that one entity provides the capability or functionality to perform renaming operations on 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.