Triple
T11815869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Longmire |
E280997
|
entity |
| Predicate | sportDisciplinePlayed |
P1080
|
FINISHED |
| Object | Australian rules football |
—
|
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: Australian rules football | Statement: [John Longmire, sportDisciplinePlayed, Australian rules football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportDisciplinePlayed Context triple: [John Longmire, sportDisciplinePlayed, Australian rules football]
-
A.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is involved.
-
B.
primarySport
chosen
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
-
C.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
-
D.
hasOlympicDiscipline
Indicates that an entity (typically a sport) includes or is associated with a specific discipline as recognized in the Olympic Games.
-
E.
sportsName
Indicates the specific sport associated with or played in a given context or 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.