Triple
T4471203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großes Festspielhaus |
E98497
|
entity |
| Predicate | hasStageWidth |
P3989
|
FINISHED |
| Object | about 100 metres |
—
|
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: about 100 metres | Statement: [Großes Festspielhaus, hasStageWidth, about 100 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageWidth Context triple: [Großes Festspielhaus, hasStageWidth, about 100 metres]
-
A.
hasWidth
chosen
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
B.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
C.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
D.
sectionWidthGranted
Indicates that a specific width has been allocated or approved for a section within a layout or structure.
-
E.
hasStageDesignElement
Indicates a relationship in which a stage production, performance, or set includes or is associated with a particular stage design element (such as props, scenery, lighting, or other visual components).
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.