Triple
T17961094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rising Pune Supergiant |
E449081
|
entity |
| Predicate | seasonResult2017 |
P117624
|
FINISHED |
| Object | runners-up |
—
|
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: runners-up | Statement: [Rising Pune Supergiant, seasonResult2017, runners-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonResult2017 Context triple: [Rising Pune Supergiant, seasonResult2017, runners-up]
-
A.
usesSeasonResults
Indicates that something bases its outcomes, decisions, or operations on the results from a particular season.
-
B.
resultForEaglesSeason
Indicates the outcome or performance result associated with a specific season of the Eagles.
-
C.
seasonWins
Indicates the number of games or competitions a team or individual has won during a specific season.
-
D.
teamOutcome
chosen
Indicates the result or consequence experienced by a team as a whole in relation to a specific event, activity, or performance.
-
E.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b132cc10819088526a0b4b098d69 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.