Triple
T26296398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loki Patera |
E661430
|
entity |
| Predicate | hasEruptionPeriodicity |
P12664
|
FINISHED |
| Object | quasi-periodic |
—
|
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: quasi-periodic | Statement: [Loki Patera, hasEruptionPeriodicity, quasi-periodic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEruptionPeriodicity Context triple: [Loki Patera, hasEruptionPeriodicity, quasi-periodic]
-
A.
hasEruptionEpisodes
Indicates that an entity (such as a volcano or geyser) undergoes one or more distinct eruption events over time.
-
B.
eruptionFrequency
chosen
Indicates how often an eruption event occurs within a given time period.
-
C.
hasFrequentEruptionsSince
Indicates that an entity has experienced eruptions repeatedly and at relatively short intervals starting from a specified point in time.
-
D.
eruptionPotential
Indicates the likelihood or capacity of something (typically a volcano or similar system) to erupt under given conditions.
-
E.
hasHistoricalEruptionsSince
Indicates that the referenced volcano or geological feature has experienced one or more recorded eruptions since a specified point in time.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eaea1d08190b93b85590b8c9781 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:12 p.m.