Triple
T3221764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panathenaic Stadium |
E67526
|
entity |
| Predicate | sportsDisciplineHosted |
P35509
|
FINISHED |
| Object | athletics |
—
|
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: athletics | Statement: [Panathenaic Stadium, sportsDisciplineHosted, athletics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsDisciplineHosted Context triple: [Panathenaic Stadium, sportsDisciplineHosted, athletics]
-
A.
sportsEventHosted
Indicates that a particular sports event was organized, arranged, or held by a specified host entity (such as a venue, organization, or city).
-
B.
hostedDiscipline
chosen
Indicates that an entity served as the host or venue for a particular discipline, event category, or field of competition.
-
C.
cohostedSportingEvents
Indicates that two or more entities jointly organized or hosted one or more sporting events together.
-
D.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
E.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is involved.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae1845408190b3eccd791231c69c |
completed | March 8, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.