Triple
T21241987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naia festival |
E523497
|
entity |
| Predicate | sportingFunction |
P137104
|
FINISHED |
| Object | athletic games in honor of Zeus |
—
|
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: athletic games in honor of Zeus | Statement: [Naia festival, sportingFunction, athletic games in honor of Zeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportingFunction Context triple: [Naia festival, sportingFunction, athletic games in honor of Zeus]
-
A.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
B.
sportCreated
Indicates that an entity is the originator or inventor of a particular sport.
-
C.
sportingMovement
Indicates a physical action or motion performed as part of a sport or athletic activity.
-
D.
sportsGround
Indicates that a location functions as a sports ground, i.e., a place designated or used for playing sports or athletic activities.
-
E.
hasSportsFunction
chosen
Indicates that an entity serves a role, purpose, or function related to sports activities or sports-related operations.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7352453f88190b38de7b0108c683a |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:47 p.m.