Triple
T17554308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American League president forfeited second game |
E427549
|
entity |
| Predicate | officialScore |
P111509
|
FINISHED |
| Object | 9–0 |
—
|
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: 9–0 | Statement: [American League president forfeited second game, officialScore, 9–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialScore Context triple: [American League president forfeited second game, officialScore, 9–0]
-
A.
scores
chosen
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.
-
B.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
C.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
D.
officialGoal
Indicates that something is the formally designated or institutionally recognized objective or target of an entity.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45620983c81909e71f938ce934efa |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.