Triple
T33413764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pal Joey |
E855655
|
entity |
| Predicate | 1952RevivalChoreographer |
P176570
|
FINISHED |
| Object | Robert Alton |
—
|
NE NERFINISHED |
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: Robert Alton | Statement: [Pal Joey, 1952RevivalChoreographer, Robert Alton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1952RevivalChoreographer Context triple: [Pal Joey, 1952RevivalChoreographer, Robert Alton]
-
A.
2012RevivalTheatre
Indicates that an entity is associated with a theatrical revival production that took place in 2012.
-
B.
2019RevivalDirector
Indicates that an entity served as the director of a 2019 revival production of another work.
-
C.
2022RevivalTheatre
Indicates a relationship where an entity is associated with a theatrical revival production that took place in the year 2022.
-
D.
revivalStars
Indicates a relationship where one entity initiates, leads, or is central to a revival, renewal, or comeback of another entity.
-
E.
revivalDirector
Indicates that one entity is the director responsible for staging or overseeing a revival (new production) of another entity, typically a work such as a play or performance.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.