Triple
T16286112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fair Play |
E395391
|
entity |
| Predicate | acquisitionReportedAmount |
P5867
|
FINISHED |
| Object | 20000000 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: 20000000 USD | Statement: [Fair Play, acquisitionReportedAmount, 20000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionReportedAmount Context triple: [Fair Play, acquisitionReportedAmount, 20000000 USD]
-
A.
acquisitionPrice
chosen
Indicates the monetary amount paid to acquire an asset, company, or item in a transaction.
-
B.
receivedSettlementAmount
Indicates that an entity has obtained a specified amount of money or value as part of a settlement.
-
C.
acquisitionAnnouncedBy
Indicates that an acquisition event was publicly announced by the specified announcing entity (such as a company or organization).
-
D.
fundingAuthorizationAmount
Indicates the specific amount of money that has been formally approved or authorized to fund something.
-
E.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24914bda08190a5d6315414ee3f76 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.