Triple
T28896416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shining series |
E732844
|
entity |
| Predicate | firstGameInSeries |
P67943
|
FINISHED |
| Object | Shining in the Darkness |
—
|
NE NERFINISHED |
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: Shining in the Darkness | Statement: [Shining series, firstGameInSeries, Shining in the Darkness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGameInSeries Context triple: [Shining series, firstGameInSeries, Shining in the Darkness]
-
A.
firstGamePlayed
Indicates the specific game that an entity participated in before any other, marking the earliest game in which it played.
-
B.
gameNumberInSeries
Indicates which numbered game within a series or sequence of games a particular game is.
-
C.
firstGameLeague
Indicates that a given league is the first league in which a particular game was played or took place.
-
D.
firstHomeRunInGame
Indicates that the referenced home run is the first one hit by that player in that particular game.
-
E.
isInauguralGameOf
chosen
Indicates that one game is the first-ever or opening game associated with a particular event, season, team, or competition.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
Created at: April 28, 2026, 7:59 a.m.