Triple
T36145221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Curtain Theatre (fictionalized) |
E1045428
|
entity |
| Predicate | stageFor |
P178136
|
FINISHED |
| Object | Romeo and Juliet (fictionalized production) |
—
|
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: Romeo and Juliet (fictionalized production) | Statement: [The Curtain Theatre (fictionalized), stageFor, Romeo and Juliet (fictionalized production)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageFor Context triple: [The Curtain Theatre (fictionalized), stageFor, Romeo and Juliet (fictionalized production)]
-
A.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
C.
stageAfter
Indicates that one stage occurs later in sequence or order than another specified stage.
-
D.
stageAct
chosen
Indicates that an entity performs or presents an act or performance on a stage before an audience.
-
E.
stageReached
Indicates that a process, task, or entity has arrived at or completed a specific stage or phase within a defined progression.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.