Triple
T20057397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curt Menefee |
E499375
|
entity |
| Predicate | worksOnSport |
P91573
|
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: [Curt Menefee, worksOnSport, American football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksOnSport Context triple: [Curt Menefee, worksOnSport, American football]
-
A.
performsAtSport
Indicates that an entity carries out or participates in an activity at a particular sport or sporting context.
-
B.
usedSportFor
Indicates that an entity employs or utilizes a particular sport as a means, tool, or context for achieving some purpose or performing an activity.
-
C.
performsForSport
chosen
Indicates that an entity carries out an action or activity specifically in the context of a particular sport.
-
D.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
E.
servesSport
Indicates that one entity provides or is used for playing, supporting, or accommodating 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6637325908190aefc0e27e2ed5750 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.