Triple
T17762699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnold Classic |
E443418
|
entity |
| Predicate | parentFestivalIncludes |
P128247
|
FINISHED |
| Object | strongman competitions |
—
|
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: strongman competitions | Statement: [Arnold Classic, parentFestivalIncludes, strongman competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentFestivalIncludes Context triple: [Arnold Classic, parentFestivalIncludes, strongman competitions]
-
A.
hasParentFestival
Indicates that a festival is part of, or derived from, a larger or primary festival that serves as its parent.
-
B.
hasParentFestivalType
Indicates that a festival is associated with or classified under a broader, parent festival type.
-
C.
parentFestivalAbbreviation
Indicates that one festival is identified by the abbreviation of its parent or overarching festival.
-
D.
mainFestival
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
-
E.
festivalPresence
Indicates that an entity is present at, participates in, or is associated with a particular festival 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485f887ac81908c896a50175692b9 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3cfab7edc8190b663282d565a0389 |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:11 a.m.