Triple
T26967140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1936 MLB All-Star Game |
E679200
|
entity |
| Predicate | inningFormat |
P2673
|
FINISHED |
| Object | 9 innings |
—
|
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 innings | Statement: [1936 MLB All-Star Game, inningFormat, 9 innings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inningFormat Context triple: [1936 MLB All-Star Game, inningFormat, 9 innings]
-
A.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
B.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
careerFormat
Indicates the specific structure or type of professional path or occupational arrangement associated with an entity.
-
D.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
E.
typicalFinalFormat
Indicates that something represents the usual or standard structure or arrangement in which an item, document, or data is ultimately presented or delivered.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621222ea88190a58d686d3b4cc802 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:36 a.m.