Triple
T3323513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maroons |
E69853
|
entity |
| Predicate | seriesWins2006to2013 |
P47283
|
FINISHED |
| Object | eight consecutive series wins |
—
|
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: eight consecutive series wins | Statement: [Maroons, seriesWins2006to2013, eight consecutive series wins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesWins2006to2013 Context triple: [Maroons, seriesWins2006to2013, eight consecutive series wins]
-
A.
seasonNumberInYear
Indicates the specific ordinal position of a season within a given year.
-
B.
seriesWinningGame
Indicates that a particular game is the decisive or clinching game in which one side wins the overall series.
-
C.
currentSeriesIntroduced
Indicates that an entity was first introduced or appeared in the currently ongoing series or installment of a work.
-
D.
seasonNumber
Indicates the ordinal position of a season within a series or sequence of seasons.
-
E.
consecutiveWinningSeasons
Indicates that an entity (such as a team or individual) has achieved winning seasons in back-to-back or uninterrupted consecutive years.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13e6c288190805f8abcd3acc906 |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.