Triple
T11808568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyōgen theatre |
E280810
|
entity |
| Predicate | usesPerformanceSpace |
P27770
|
FINISHED |
| Object | Noh stage |
—
|
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: Noh stage | Statement: [Kyōgen theatre, usesPerformanceSpace, Noh stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPerformanceSpace Context triple: [Kyōgen theatre, usesPerformanceSpace, Noh stage]
-
A.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
B.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
-
C.
publicSpacesUsed
Indicates that certain public spaces are being utilized or occupied for a particular purpose or activity.
-
D.
performanceSpaceType
chosen
Indicates the specific kind or category of space in which a performance or event takes place.
-
E.
hasOffAxisPerformance
Indicates that an entity exhibits specific behavior or performance characteristics when observed or operated from an angle that is not aligned with its primary or intended axis.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.