Triple
T20307889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y Kant Tori Read |
E510152
|
entity |
| Predicate | originalCommercialPerformance |
P139608
|
FINISHED |
| Object | poor |
—
|
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: poor | Statement: [Y Kant Tori Read, originalCommercialPerformance, poor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCommercialPerformance Context triple: [Y Kant Tori Read, originalCommercialPerformance, poor]
-
A.
hasCommercialPerformance
Indicates that an entity’s success or outcome is characterized in terms of its performance in the commercial or market context (e.g., sales, revenue, or profitability).
-
B.
originalPerformanceFor
Indicates that one entity is the original performance or execution from which another related version, recording, or representation is derived.
-
C.
broadwayCommercialOutcome
Indicates the commercial result or financial performance associated with a Broadway production or run.
-
D.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
E.
performances
Indicates that an entity stages, presents, or executes artistic or entertainment events for an audience.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677411cf08190ba7e98a4135b643a |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:18 a.m.