Triple
T29958013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arch Stage |
E760961
|
entity |
| Predicate | belongsToFestivalBrand |
P15226
|
FINISHED |
| Object | Tomorrowland |
—
|
NE NERFINISHED |
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: Tomorrowland | Statement: [The Arch Stage, belongsToFestivalBrand, Tomorrowland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToFestivalBrand Context triple: [The Arch Stage, belongsToFestivalBrand, Tomorrowland]
-
A.
hasEventBrand
chosen
Indicates that an event is associated with or organized under a particular brand.
-
B.
hasFestivalConnection
Indicates a relationship in which two entities are connected through a festival, such as by participation, organization, sponsorship, or association with that event.
-
C.
hasParentFestival
Indicates that a festival is part of, or derived from, a larger or primary festival that serves as its parent.
-
D.
hasParentFestivalType
Indicates that a festival is associated with or classified under a broader, parent festival type.
-
E.
linkedFestivalStatus
Indicates that one entity’s festival status is directly connected to or dependent on another entity’s festival status.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: April 29, 2026, 6:27 p.m.