Triple
T33413735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pal Joey |
E855655
|
entity |
| Predicate | originalBroadwayBookWriter |
P99078
|
FINISHED |
| Object | John O’Hara |
E269663
|
NE 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: John O’Hara | Statement: [Pal Joey, originalBroadwayBookWriter, John O’Hara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBroadwayBookWriter Context triple: [Pal Joey, originalBroadwayBookWriter, John O’Hara]
-
A.
broadwaySourceWrittenBy
chosen
Indicates that the source material for a Broadway production was written by the specified creator.
-
B.
producedOnBroadwayBy
Indicates that a theatrical production was staged on Broadway under the responsibility or auspices of a specific producer or producing entity.
-
C.
originalBroadwayStar
Indicates that the subject was a member of the original Broadway cast in the specified role or production.
-
D.
wroteForBroadway
Indicates that a person created or co-created a written work (such as a script, score, or lyrics) specifically for a Broadway production.
-
E.
originalBroadwayCoStar
Indicates that two performers appeared together as co-stars in the original Broadway production of the same show.
- F. None of above.
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_6a031b40c6d0819096f4b9787a1f09d1 |
completed | May 12, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3576fee9a881908d22f8dc48ced2dd |
completed | June 19, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_6a03191f8ee08190b3416b044869ddfd |
completed | May 12, 2026, 12:12 p.m. |
Created at: May 1, 2026, 1:36 a.m.