Triple
T30053500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Norton vs. George Foreman |
E763662
|
entity |
| Predicate | undercardFeature |
P102670
|
FINISHED |
| Object | local Venezuelan fighters |
—
|
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: local Venezuelan fighters | Statement: [Ken Norton vs. George Foreman, undercardFeature, local Venezuelan fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undercardFeature Context triple: [Ken Norton vs. George Foreman, undercardFeature, local Venezuelan fighters]
-
A.
undercard
chosen
Indicates that one event, match, or performance is scheduled to occur before and in support of a main or headline event within the same program or card.
-
B.
undercardNotable
Indicates that an undercard match or participant is considered especially noteworthy or significant within the event’s lineup.
-
C.
cardVariant
Indicates that one card is a specific version or variation of another base card.
-
D.
presentedUnderBanner
Indicates that something is displayed or showcased beneath or associated with a specific banner or heading.
-
E.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 6:56 p.m.