Triple
T25523927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koodiyattam |
E639727
|
entity |
| Predicate | requiresSpace |
P47152
|
FINISHED |
| Object | specially designed temple theatre halls |
—
|
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: specially designed temple theatre halls | Statement: [Koodiyattam, requiresSpace, specially designed temple theatre halls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSpace Context triple: [Koodiyattam, requiresSpace, specially designed temple theatre halls]
-
A.
usesSpace
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with another entity.
-
B.
hasSpaceIn
Indicates that one entity occupies or is contained within a physical or conceptual space provided by another entity.
-
C.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
D.
spaceRequirements
chosen
Indicates the amount and type of physical or storage space needed for something to be properly placed, installed, or operated.
-
E.
hasSpaceBetweenElements
Indicates that there is a physical or conceptual gap or separation between the referenced elements.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 3:08 p.m.