Triple
T36674075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outlook Festival |
E905495
|
entity |
| Predicate | hasRelatedFestival |
P136413
|
FINISHED |
| Object | Dimensions Festival |
E905496
|
NE 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: Dimensions Festival | Statement: [Outlook Festival, hasRelatedFestival, Dimensions Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedFestival Context triple: [Outlook Festival, hasRelatedFestival, Dimensions Festival]
-
A.
hasFestivalConnection
chosen
Indicates a relationship in which two entities are connected through a festival, such as by participation, organization, sponsorship, or association with that event.
-
B.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
C.
hasParentFestival
Indicates that a festival is part of, or derived from, a larger or primary festival that serves as its parent.
-
D.
hasFestivalDepicted
Indicates that a work or representation includes a depiction or portrayal of a festival.
-
E.
hasFestivalSection
Indicates that something includes or is associated with a specific section or category within a festival.
- F. None of above.
Provenance (4 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20da0cd8819090b6c0d0df607128 |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.