Triple
T11907091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primeval Whirl |
E283297
|
entity |
| Predicate | operatedSeasonallyFrom |
P102281
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Primeval Whirl, operatedSeasonallyFrom, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedSeasonallyFrom Context triple: [Primeval Whirl, operatedSeasonallyFrom, 2012]
-
A.
operatedSeason
Indicates the specific season or time period during which an entity (such as a service, facility, or operation) was active or in use.
-
B.
operatedFrom
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
C.
isSeasonalStandard
Indicates that something follows or conforms to the standard conditions, rules, or patterns that apply only during a specific season or time period.
-
D.
seasonOpeningOrClosing
Indicates that an event marks either the beginning or the end of a particular season.
-
E.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5264b2081909bda6c24abb89725 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.