Triple
T21722563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Against All Odds |
E536195
|
entity |
| Predicate | sportsElement |
P52152
|
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: [Against All Odds, sportsElement, American football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsElement Context triple: [Against All Odds, sportsElement, American football]
-
A.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
B.
sportsModel
Indicates a relationship where an entity is a sports-oriented model or variant of another entity (such as a product, design, or system) optimized or styled for sporting use.
-
C.
sportSection
Indicates that something belongs to, appears in, or is categorized under the sports section of a larger collection or publication.
-
D.
sportsCategory
chosen
Indicates that one entity is classified as a type or category within the domain of sports to which the other entity belongs.
-
E.
sportCreated
Indicates that an entity is the originator or inventor of 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd97032c08190820b87a288e77293 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.