Triple
T222016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Yankees vs Baltimore Orioles |
E4233
|
entity |
| Predicate | gameFormat |
P2673
|
FINISHED |
| Object | nine-inning games |
—
|
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: nine-inning games | Statement: [New York Yankees vs Baltimore Orioles, gameFormat, nine-inning games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameFormat Context triple: [New York Yankees vs Baltimore Orioles, gameFormat, nine-inning games]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
C.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
gameWinningScoreType
Indicates the type or category of score (e.g., goal, point, run) that results in winning a game.
-
E.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c705fd88190bfee7f5e1f7cee17 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5617788190814358aee3f7ae37 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.