Triple
T15530428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ice Flower |
E370197
|
entity |
| Predicate | isRecurrence |
P16303
|
FINISHED |
| Object | recurring item in Mario series |
—
|
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: recurring item in Mario series | Statement: [Ice Flower, isRecurrence, recurring item in Mario series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecurrence Context triple: [Ice Flower, isRecurrence, recurring item in Mario series]
-
A.
recurrenceType
Indicates the pattern or frequency with which an event or action repeats over time.
-
B.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
C.
recurringEvent
chosen
Indicates that an event occurs repeatedly over time according to some regular pattern or schedule.
-
D.
satisfiesRecurrence
Indicates that one entity fulfills or conforms to a specified recurrence relation defined by another entity.
-
E.
recurrence
Indicates that an event, condition, or state happens again or repeatedly over time, often after a period of absence or resolution.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414773548190b3311515f9d957dd |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.