Triple
T526158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Phryge |
E10922
|
entity |
| Predicate | associatedWithSport |
P5085
|
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: [Olympic Phryge, associatedWithSport, athletics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSport Context triple: [Olympic Phryge, associatedWithSport, athletics]
-
A.
sportingAssociation
Indicates a formal relationship in which an organization serves as a governing, organizing, or affiliating body for sports activities, teams, or events.
-
B.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
C.
sportsAssociation
Indicates a formal relationship in which an entity is affiliated with, governed by, or participates under the auspices of a specific sports organization or governing body.
-
D.
appliesToSports
chosen
Indicates that something is relevant, appropriate, or specifically intended for use in the context of sports.
-
E.
associatedWithCompetition
Indicates that there is a relationship or involvement between an entity and a specific competition or competitive event.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d0d22081908aad915482d39e74 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.