Triple
T10509478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Stadium |
E247872
|
entity |
| Predicate | firstSelloutInStreak |
P86302
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Memorial Stadium, firstSelloutInStreak, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSelloutInStreak Context triple: [Memorial Stadium, firstSelloutInStreak, 1962]
-
A.
selloutStreakStartYear
chosen
Indicates the year in which a continuous streak of sold-out events or performances began.
-
B.
firstEditionSoldOutTime
Indicates the point in time at which the first edition of an item became completely sold out.
-
C.
hittingStreakStartDate
Indicates the date on which a continuous sequence of successful hits (a hitting streak) begins.
-
D.
streak
Indicates that an entity is experiencing a continuous run of the same outcome or behavior across multiple consecutive events or time points.
-
E.
longestUnbeatenStreak
Indicates the relationship where an entity holds the greatest continuous sequence of events (such as games or matches) without a loss compared to others.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b359ac8190b3683cc6b9c70a71 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.