Triple
T1614153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill |
E34675
|
entity |
| Predicate | leadPerformanceDescribedAs |
P30438
|
FINISHED |
| Object | critically acclaimed |
—
|
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: critically acclaimed | Statement: [Bill, leadPerformanceDescribedAs, critically acclaimed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadPerformanceDescribedAs Context triple: [Bill, leadPerformanceDescribedAs, critically acclaimed]
-
A.
leadSingle
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
-
B.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
C.
featuresPerformanceBy
Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
-
D.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
E.
responseLedBy
Indicates that a particular response, initiative, or action is directed, coordinated, or overseen by a specified leading entity.
- F. None of above. chosen
Provenance (4 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a93fedcb108190ad91f938d5eeaaa2 |
completed | March 5, 2026, 8:33 a.m. |
Created at: March 4, 2026, 7:28 p.m.