Triple
T2647162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Rodriguez |
E53810
|
entity |
| Predicate | notableContractValue |
P482
|
FINISHED |
| Object | 252000000 |
—
|
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: 252000000 | Statement: [Alex Rodriguez, notableContractValue, 252000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableContractValue Context triple: [Alex Rodriguez, notableContractValue, 252000000]
-
A.
notableContract
Indicates that there exists a contract or agreement between entities that is of particular significance, prominence, or public interest.
-
B.
notableTransaction
Indicates that a transaction between entities is significant or noteworthy in context, such as being unusually large, important, or otherwise exceptional.
-
C.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
D.
monetaryValue
chosen
Indicates the amount of money associated with an entity, event, or transaction.
-
E.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd919bf2c81908feb768f3391e985 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.