Triple
T29140743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arthur Haynes Show (appearances) |
E738623
|
entity |
| Predicate | hasLeadSeriesStar |
P152309
|
FINISHED |
| Object | Arthur Haynes |
—
|
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: Arthur Haynes | Statement: [The Arthur Haynes Show (appearances), hasLeadSeriesStar, Arthur Haynes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadSeriesStar Context triple: [The Arthur Haynes Show (appearances), hasLeadSeriesStar, Arthur Haynes]
-
A.
hasLeadInSeries
chosen
Indicates that one entity serves as the primary or starring role in a series associated with another entity.
-
B.
hasRumoredLeadActor
Indicates that an entity (such as a film or show) is associated with a person who is speculated or reported, but not confirmed, to be its lead actor.
-
C.
starredActorWith
Indicates that one entity participated as an actor in a production together with another specified actor.
-
D.
hasDirectorStar
Indicates that a person both directed and starred in the same work (e.g., film, show, or production).
-
E.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 11:36 a.m.