Triple
T4741393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Williams |
E105250
|
entity |
| Predicate | RBI |
P49076
|
FINISHED |
| Object | 1839 career runs batted in |
—
|
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: 1839 career runs batted in | Statement: [Ted Williams, RBI, 1839 career runs batted in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RBI Context triple: [Ted Williams, RBI, 1839 career runs batted in]
-
A.
centralBank
Indicates that an entity functions as the primary monetary authority responsible for issuing currency and implementing monetary policy for a specific jurisdiction.
-
B.
RBIInCareer
chosen
Indicates the total number of runs batted in (RBIs) a player has accumulated over their entire career.
-
C.
banking
Indicates that an entity provides or engages in financial services such as holding deposits, managing accounts, or facilitating monetary transactions for another entity.
-
D.
monetaryAuthorityAbbreviation
Indicates the standard shortened form or acronym used to refer to a particular monetary authority.
-
E.
previousMonetaryAuthority
Indicates that one entity served as the monetary authority immediately before another entity in a temporal sequence.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a5f3548190a6acf1dcfd64d11d |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.