Triple
T35754056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Beijing ePrix |
E1033391
|
entity |
| Predicate | openingRaceOfSeason |
P109350
|
FINISHED |
| Object | 2014–15 Formula E season |
—
|
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: 2014–15 Formula E season | Statement: [2014 Beijing ePrix, openingRaceOfSeason, 2014–15 Formula E season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingRaceOfSeason Context triple: [2014 Beijing ePrix, openingRaceOfSeason, 2014–15 Formula E season]
-
A.
openingSeason
Indicates that an entity marks the beginning or first season of another entity, such as a series, event, or competition.
-
B.
openingRace
chosen
Indicates that one race serves as the initial or first event in a sequence of races or a racing competition.
-
C.
openingForSeason
Indicates the event or action of beginning a new operational or active season for something (such as a venue, activity, or service).
-
D.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
E.
openSeasonally
Indicates that an entity operates or is accessible only during specific seasons or times of the year.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:06 p.m.