Triple
T36951166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Orange Bowl |
E914065
|
entity |
| Predicate | payoutPerTeam |
P150128
|
FINISHED |
| Object | 17000000 |
—
|
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: 17000000 | Statement: [2008 Orange Bowl, payoutPerTeam, 17000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payoutPerTeam Context triple: [2008 Orange Bowl, payoutPerTeam, 17000000]
-
A.
payingPlayers
Indicates that one or more entities are making a payment to one or more players, typically as compensation, fees, or rewards.
-
B.
awardedToEach
chosen
Indicates that something (such as a prize, benefit, or recognition) is given individually to every member of a specified group.
-
C.
memberRemuneration
Indicates that a member receives payment or compensation, typically for their role, services, or participation within an organization or group.
-
D.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
E.
hasPayout
Indicates that one entity provides or is associated with a monetary or value-based payout to another entity.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.