Triple
T31572660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hack Wilson |
E805605
|
entity |
| Predicate | RBIRecord |
P171973
|
FINISHED |
| Object | 191 RBIs in a single MLB season |
—
|
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: 191 RBIs in a single MLB season | Statement: [Hack Wilson, RBIRecord, 191 RBIs in a single MLB season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RBIRecord Context triple: [Hack Wilson, RBIRecord, 191 RBIs in a single MLB season]
-
A.
recordStructure
Indicates a relationship where an entity defines, organizes, or specifies the internal layout and components of a record or data structure.
-
B.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
-
C.
RBIleader
Indicates that the subject is the leader or head of the Reserve Bank of India (RBI) in relation to the object.
-
D.
recordClass
Indicates that one entity is classified or categorized as a particular type or class within a record or recording system.
-
E.
recordsObject
Indicates that one entity creates or maintains a record of another entity as its subject or content.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:20 p.m.