Triple
T49337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankees–Red Sox rivalry |
E969
|
entity |
| Predicate | historicalMilestone |
P2107
|
FINISHED |
| Object | Red Sox comeback from 0–3 deficit in 2004 ALCS |
—
|
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: Red Sox comeback from 0–3 deficit in 2004 ALCS | Statement: [Yankees–Red Sox rivalry, historicalMilestone, Red Sox comeback from 0–3 deficit in 2004 ALCS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMilestone Context triple: [Yankees–Red Sox rivalry, historicalMilestone, Red Sox comeback from 0–3 deficit in 2004 ALCS]
-
A.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
E.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.