Triple
T20315415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival Republic |
E510365
|
entity |
| Predicate | hasFeatureAtEvents |
P6628
|
FINISHED |
| Object | multiple performance stages |
—
|
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: multiple performance stages | Statement: [Festival Republic, hasFeatureAtEvents, multiple performance stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatureAtEvents Context triple: [Festival Republic, hasFeatureAtEvents, multiple performance stages]
-
A.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
B.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
-
C.
featuresEvent
chosen
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
D.
hasEventFrequency
Indicates how often a particular event occurs within a given time period.
-
E.
accessibleForEventType
Indicates that something can be used, reached, or is available in the context of a specified type or category of event.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67786f4dc8190b02a6c2a4338362d |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.