Triple
T12822501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texaco Metropolitan Opera radio broadcasts |
E306564
|
entity |
| Predicate | notableSponsorDuration |
P42331
|
FINISHED |
| Object | over six decades |
—
|
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: over six decades | Statement: [Texaco Metropolitan Opera radio broadcasts, notableSponsorDuration, over six decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSponsorDuration Context triple: [Texaco Metropolitan Opera radio broadcasts, notableSponsorDuration, over six decades]
-
A.
sponsoredNamePeriod
Indicates a time-bounded period during which an entity’s name is officially sponsored or branded by another party.
-
B.
sponsorshipNameSince
Indicates the date or time from which a particular sponsorship name has been in effect for the associated entity or relationship.
-
C.
sponsorshipEra
chosen
Indicates the time period during which a sponsorship relationship is in effect between parties.
-
D.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
E.
sponsorshipEndedWith
Indicates that a previously existing sponsorship relationship between entities has come to an end.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9fcc8c8190a926ab0481d28f14 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:32 p.m.