Triple
T1502574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hondo |
E33827
|
entity |
| Predicate | famousPlay |
P29422
|
FINISHED |
| Object | Havlicek stole the ball |
—
|
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: Havlicek stole the ball | Statement: [Hondo, famousPlay, Havlicek stole the ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousPlay Context triple: [Hondo, famousPlay, Havlicek stole the ball]
-
A.
notablePlaywrightProduced
Indicates that a notable playwright created or authored the referenced play or dramatic work.
-
B.
theaterWork
Indicates a relationship where an entity is a theatrical work (such as a play or stage production) associated with another entity, typically as its subject, creator, or context.
-
C.
originalBroadwayStar
Indicates that the subject was a member of the original Broadway cast in the specified role or production.
-
D.
dramaticRole
Indicates that one entity serves as a character or part played by another entity within a dramatic or theatrical work.
-
E.
theatricalFunction
Indicates the role or purpose something serves within a theatrical context, such as its function in staging, performance, or dramatic presentation.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
| PDg | Predicate description generation | batch_69a90582f2548190bc0a6bdcd6d9d015 |
completed | March 5, 2026, 4:24 a.m. |
Created at: March 4, 2026, 7:24 p.m.