Triple
T17320780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Giants won 2–1 |
E420553
|
entity |
| Predicate | seriesScore |
P126966
|
FINISHED |
| Object | 2–1 |
—
|
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: 2–1 | Statement: [New York Giants won 2–1, seriesScore, 2–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesScore Context triple: [New York Giants won 2–1, seriesScore, 2–1]
-
A.
notableSeriesScore
Indicates that there is a notable or significant score associated with a particular series, typically highlighting its importance or prominence relative to other series.
-
B.
scores
Indicates that one entity achieves or is assigned a numerical result, rating, or points in relation to another entity, such as a test, game, or evaluation.
-
C.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
D.
isPartOfScoreBy
Indicates that something constitutes a component or segment within a larger score or musical composition.
-
E.
seriesScoreBeforeGame
Indicates the cumulative score or standing in a series between competitors as it existed prior to a specific game being played.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439cf5394819089bff5f8dc2e8241 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.