Triple
T15974080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lion of Athens |
E387398
|
entity |
| Predicate | hasSportContext |
P46432
|
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: [The Lion of Athens, hasSportContext, athletics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportContext Context triple: [The Lion of Athens, hasSportContext, athletics]
-
A.
hasSportingContext
chosen
Indicates that something is associated with, occurs within, or is relevant to a particular sporting or athletic context.
-
B.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
C.
hasCompetitionContext
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
-
D.
hasSportsRole
Indicates that an entity holds or is assigned a specific role or position within a sports context or organization.
-
E.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.