Triple
T33405351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theaterama |
E855422
|
entity |
| Predicate | complexComponentType |
P6678
|
FINISHED |
| Object | pavilion component |
—
|
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: pavilion component | Statement: [Theaterama, complexComponentType, pavilion component]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexComponentType Context triple: [Theaterama, complexComponentType, pavilion component]
-
A.
componentType
chosen
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
B.
complexName
Indicates that an entity has a multi-part or structurally intricate name, typically composed of several elements or components.
-
C.
coreComplexDesign
Indicates that an entity is responsible for or involved in the design of a core complex or central architectural component of a system.
-
D.
featuresComplexCompositions
Indicates that the subject includes or presents compositions that are intricate, multi-layered, or structurally sophisticated.
-
E.
complexUnified
Indicates that multiple distinct components or aspects are integrated into a single, cohesive and interdependent whole.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:36 a.m.