Triple
T13571868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobblers |
E324181
|
entity |
| Predicate | participatesInSport |
P67409
|
FINISHED |
| Object | American 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: American football | Statement: [Cobblers, participatesInSport, American football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatesInSport Context triple: [Cobblers, participatesInSport, American football]
-
A.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
-
B.
primarySport
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
-
C.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
D.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
E.
relatedSport
chosen
Indicates that there is an association or connection between an entity and a particular sport.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0106cb48190b20eb9bda131a68a |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.