Triple
T25764899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 All-Star Game |
E648853
|
entity |
| Predicate | runTimeInnings |
P123915
|
FINISHED |
| Object | 9 |
—
|
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 | Statement: [1974 All-Star Game, runTimeInnings, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runTimeInnings Context triple: [1974 All-Star Game, runTimeInnings, 9]
-
A.
numberOfInningsPerSide
chosen
Indicates the number of innings that each side or team is allotted to play in a game or match.
-
B.
numberOfBallsPerInnings
Indicates the quantity of balls delivered or played during a single innings.
-
C.
totalRunsScored
Indicates the total number of runs that have been scored by a specified entity (such as a player or team) over a defined context or period.
-
D.
typicalInningsOversLimit
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
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.
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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf2b7f48190bc8fdef839e9d005 |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:09 a.m.