Triple
T12014497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhammad Ali vs. George Foreman |
E285988
|
entity |
| Predicate | purseForeman |
P102788
|
FINISHED |
| Object | 5000000 USD |
—
|
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: 5000000 USD | Statement: [Muhammad Ali vs. George Foreman, purseForeman, 5000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purseForeman Context triple: [Muhammad Ali vs. George Foreman, purseForeman, 5000000 USD]
-
A.
purseRecord
Indicates a record or log entry that captures the state, contents, or transactions associated with a purse or similar container of funds.
-
B.
purseGeorgeForeman
Indicates that an entity is pursuing, seeking, or going after George Foreman, typically in a competitive, legal, or goal-oriented context.
-
C.
purse
Indicates attempting to influence or persuade someone to adopt a particular course of action, belief, or decision.
-
D.
pouch
Indicates that one entity is contained or stored within the pouch or pocket of another entity.
-
E.
PSE
Indicates a relationship where one entity is engaged in or associated with a public service or public sector employment role relative to another entity or context.
- F. None of above. chosen
Provenance (4 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:46 p.m.