Triple
T32384678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Asian theatre |
E827515
|
entity |
| Predicate | employsStageConvention |
P180662
|
FINISHED |
| Object | minimalist stage design |
—
|
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: minimalist stage design | Statement: [East Asian theatre, employsStageConvention, minimalist stage design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsStageConvention Context triple: [East Asian theatre, employsStageConvention, minimalist stage design]
-
A.
usedStageNameUntil
Indicates that an entity used a particular stage name up to a specified point in time, after which it was no longer used.
-
B.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
-
C.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
E.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 12:51 a.m.