Triple
T16019979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Caroline |
E388573
|
entity |
| Predicate | traditionallyPlayedInInning |
P121388
|
FINISHED |
| Object | eighth inning |
—
|
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: eighth inning | Statement: [Sweet Caroline, traditionallyPlayedInInning, eighth inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPlayedInInning Context triple: [Sweet Caroline, traditionallyPlayedInInning, eighth inning]
-
A.
usesInnings
Indicates that one entity employs or incorporates another entity within the context or structure of innings (e.g., in a game, match, or statistical framework).
-
B.
halfInning
Indicates the specific offensive or defensive segment of an inning in a game, typically distinguishing the top (visiting team at bat) from the bottom (home team at bat).
-
C.
numberOfBallsPerInnings
Indicates the quantity of balls delivered or played during a single innings.
-
D.
Game7Innings
Indicates that the game consists of, or is scheduled to last, seven innings.
-
E.
tieInnings
Indicates that two or more teams or players have finished an innings with the same score, resulting in no winner for that innings.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e185879c10819080a18e24969b5a6d |
completed | April 17, 2026, 12:57 a.m. |
Created at: April 10, 2026, 4:55 a.m.