Triple
T24766413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manny Pacquiao vs. Oscar De La Hoya |
E619594
|
entity |
| Predicate | contractWeight |
P157716
|
FINISHED |
| Object | 147 pounds |
—
|
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: 147 pounds | Statement: [Manny Pacquiao vs. Oscar De La Hoya, contractWeight, 147 pounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractWeight Context triple: [Manny Pacquiao vs. Oscar De La Hoya, contractWeight, 147 pounds]
-
A.
contractSize
Indicates the quantity or volume of the underlying asset specified in a single contract.
-
B.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
C.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
D.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
-
E.
contractSizeBasedOn
Indicates that the size or quantity specified in a contract is determined or calculated based on another referenced factor or entity.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 4:28 a.m.