Triple
T25509451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Theatre |
E639332
|
entity |
| Predicate | playStaged |
P9844
|
FINISHED |
| Object | Tamburlaine |
—
|
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: Tamburlaine | Statement: [Rose Theatre, playStaged, Tamburlaine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playStaged Context triple: [Rose Theatre, playStaged, Tamburlaine]
-
A.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
B.
playbackTrigger
Indicates that one event or condition causes the initiation or resumption of media playback.
-
C.
play
Indicates that an entity engages in a recreational, performative, or competitive activity, often involving a game, sport, or musical performance, typically with another entity or object.
-
D.
playsProfessional
Indicates that one entity participates in a sport, game, or performance at a professional level for compensation or as a primary occupation in relation to another entity (such as a team, league, or organization).
-
E.
plays
chosen
Indicates that an entity engages in or performs an activity, game, role, or piece of music.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80844488190bbbaa6bd2e487940 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 2:48 p.m.