Triple
T31201772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Theatre (Budapest) |
E795493
|
entity |
| Predicate | hasStageTechnology |
P133726
|
FINISHED |
| Object | modern stage machinery |
—
|
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: modern stage machinery | Statement: [National Theatre (Budapest), hasStageTechnology, modern stage machinery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageTechnology Context triple: [National Theatre (Budapest), hasStageTechnology, modern stage machinery]
-
A.
hasTechnologySystem
chosen
Indicates that one entity possesses, utilizes, or is supported by a particular technology system.
-
B.
hasTechnologyDomain
Indicates that an entity is associated with, operates within, or is relevant to a particular field or domain of technology.
-
C.
hasInteractiveTechnology
Indicates that an entity is equipped with or incorporates technology enabling user interaction or responsive engagement.
-
D.
hasTechnologyBasis
Indicates that something is founded upon, derived from, or fundamentally enabled by a particular technology.
-
E.
hasTechnologyTheme
Indicates that something is associated with, centers on, or prominently features technology as a primary theme or subject.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 29, 2026, 9:09 p.m.