Triple
T19930300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatro del Mondo |
E479032
|
entity |
| Predicate | existenceType |
P84858
|
FINISHED |
| Object | temporary installation |
—
|
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: temporary installation | Statement: [Teatro del Mondo, existenceType, temporary installation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existenceType Context triple: [Teatro del Mondo, existenceType, temporary installation]
-
A.
existsAs
Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
-
B.
existsOnlyAs
chosen
Indicates that the subject exists solely in a particular form, state, or context specified by the object, and not in any other.
-
C.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
D.
existsPrimarilyAs
Indicates that one entity’s main or fundamental mode of being or manifestation is in the form of another specified entity or state.
-
E.
hasExistentiale
Indicates that an entity possesses or is associated with an existential characteristic, condition, or mode of being.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a13265c8190bc01d3af5bd658d7 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.