Triple
T27074896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Cashen |
E685429
|
entity |
| Predicate | notablePlayerAcquisition |
P71321
|
FINISHED |
| Object | Keith Hernandez |
—
|
NE NERFINISHED |
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: Keith Hernandez | Statement: [Frank Cashen, notablePlayerAcquisition, Keith Hernandez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerAcquisition Context triple: [Frank Cashen, notablePlayerAcquisition, Keith Hernandez]
-
A.
acquiredPlayersFrom
chosen
Indicates that one entity obtained players from another entity, typically through a transfer, trade, or purchase.
-
B.
notableDraftPick
Indicates that an entity was a particularly significant or distinguished selection in a draft event (such as a sports or professional draft).
-
C.
notableTransferWindow
Indicates that a transfer window (period for player transfers) is regarded as particularly significant or noteworthy in some context.
-
D.
teamMovement
Indicates that a group or team changes its location or position together as a coordinated unit.
-
E.
teamAcquisitionInvolved
Indicates that an entity is involved in the process or event of acquiring a team (e.g., as acquirer, target, or participant).
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 27, 2026, 8:30 a.m.