Triple
T6759600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie McCovey |
E154555
|
entity |
| Predicate | RBILeader |
P73327
|
FINISHED |
| Object | National League RBI leader 1968 |
—
|
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: National League RBI leader 1968 | Statement: [Willie McCovey, RBILeader, National League RBI leader 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RBILeader Context triple: [Willie McCovey, RBILeader, National League RBI leader 1968]
-
A.
RBIleader
Indicates that the subject is the leader or head of the Reserve Bank of India (RBI) in relation to the object.
-
B.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
C.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
-
D.
designatedLeader
Indicates that one entity has been formally chosen or assigned to serve as the leader of another entity or group.
-
E.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d3264b7481908816a4d19543fb7b |
completed | March 27, 2026, 6:57 p.m. |
Created at: March 27, 2026, 2:12 p.m.