Triple
T27773158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Inches" locker room speech |
E701810
|
entity |
| Predicate | occursInSport |
P5086
|
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: ["Inches" locker room speech, occursInSport, American football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInSport Context triple: ["Inches" locker room speech, occursInSport, American football]
-
A.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
B.
usedInSport
chosen
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
C.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
D.
representsInSport
Indicates that one entity serves as an official representative of another entity within the context of a particular sport or sporting domain.
-
E.
performsAtSport
Indicates that an entity carries out or participates in an activity at a particular sport or sporting context.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 4:36 p.m.