Triple
T3350527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forum |
E70480
|
entity |
| Predicate | relationToMainFestival |
P47402
|
FINISHED |
| Object | parallel section |
—
|
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: parallel section | Statement: [Forum, relationToMainFestival, parallel section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToMainFestival Context triple: [Forum, relationToMainFestival, parallel section]
-
A.
mainFestival
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
-
B.
linkedFestival
Indicates that two entities are associated through a common festival, event, or celebration.
-
C.
peerFestival
Indicates that two festivals are considered peers, sharing a comparable status, scale, or role within a given context.
-
D.
positionInFestival
Indicates the specific role, slot, or placement an entity holds within the structure or schedule of a festival.
-
E.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
- F. None of above. chosen
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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb220721c81909eb4d8d35c923927 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.