Triple
T34034622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean O'Casey |
E872755
|
entity |
| Predicate | wrotePlaySetIn |
P12690
|
FINISHED |
| Object | Dublin |
—
|
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: Dublin | Statement: [Sean O'Casey, wrotePlaySetIn, Dublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrotePlaySetIn Context triple: [Sean O'Casey, wrotePlaySetIn, Dublin]
-
A.
wroteForBroadway
Indicates that a person created or co-created a written work (such as a script, score, or lyrics) specifically for a Broadway production.
-
B.
theatricalSetting
chosen
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
C.
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.
-
D.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
E.
implementedInTheatre
Indicates that an event, work, or action is carried out, performed, or realized within a theatre setting.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.