Triple
T33421053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL MVP |
E855844
|
entity |
| Predicate | notableVoters |
P206461
|
FINISHED |
| Object | Baseball writers |
—
|
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: Baseball writers | Statement: [NL MVP, notableVoters, Baseball writers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVoters Context triple: [NL MVP, notableVoters, Baseball writers]
-
A.
notableVote
Indicates that an entity cast a vote in a decision or election that is considered especially significant or noteworthy.
-
B.
numberOfVoters
Indicates the total count of individuals who participated in a particular vote or election.
-
C.
notableParty
Indicates that an entity is a significant or noteworthy participant in an event, activity, or relationship.
-
D.
notableProponent
Indicates that an entity is a well-known advocate or supporter of another entity, idea, or practice.
-
E.
notableElectionPerformance
Indicates that an entity achieved a particularly significant or distinguished result in an election, such as an unusually high vote share, major upset, or landmark outcome.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:36 a.m.