Triple
T16909199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinker to Evers to Chance double-play combination |
E410149
|
entity |
| Predicate | position2 |
P5131
|
FINISHED |
| Object | second baseman |
—
|
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: second baseman | Statement: [Tinker to Evers to Chance double-play combination, position2, second baseman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: position2 Context triple: [Tinker to Evers to Chance double-play combination, position2, second baseman]
-
A.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
B.
positionA
chosen
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3bdc3081908a9b4f6e63405348 |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.