Triple
T14145798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | spring classics |
E350544
|
entity |
| Predicate | importanceInSeason |
P112993
|
FINISHED |
| Object | early form indicator for riders |
—
|
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: early form indicator for riders | Statement: [spring classics, importanceInSeason, early form indicator for riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInSeason Context triple: [spring classics, importanceInSeason, early form indicator for riders]
-
A.
hasRegularSeasonImportance
Indicates that something possesses significance or relevance specifically within the context of a regular season.
-
B.
importanceInLap
Indicates the degree to which something is significant or influential within a specific lap or iteration of an event or process.
-
C.
positionInSeason
Indicates the specific ordinal placement or ranking of something within the sequence of items in a season.
-
D.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
E.
hasImportantSeason
Indicates that an entity experiences a particular season or time period that is especially significant or notable for it.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de612266248190a8591b646fe30ae6 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:53 a.m.