Triple
T13481928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandon Crawford |
E318391
|
entity |
| Predicate | battedCleanupInDebut |
P110558
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Brandon Crawford, battedCleanupInDebut, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedCleanupInDebut Context triple: [Brandon Crawford, battedCleanupInDebut, false]
-
A.
battedCleanupFor
Indicates that one entity served as the cleanup hitter (typically batting fourth) in the lineup for a particular team or another entity in a baseball context.
-
B.
battedLeadoff
Indicates that an entity served as the first batter in the lineup for a team in a particular game or context.
-
C.
battedBy
Indicates that an entity is the one who performed the batting action on another entity (e.g., a ball being batted by a player).
-
D.
battedIn
Indicates that one participant caused a run to score in a baseball context, typically by successfully hitting the ball so that a runner crosses home plate.
-
E.
battedBehind
Indicates that one participant took their turn to bat after another participant in a batting order.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3868ec8190a6a1803018d4f2d8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:42 p.m.