Triple
T26296413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loki Patera |
E661430
|
entity |
| Predicate | hasDominantComposition |
P59278
|
FINISHED |
| Object | silicate lava |
—
|
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: silicate lava | Statement: [Loki Patera, hasDominantComposition, silicate lava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantComposition Context triple: [Loki Patera, hasDominantComposition, silicate lava]
-
A.
dominantComposition
chosen
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
-
B.
hasDominantUse
Indicates that one use or function of an entity is primary or prevailing over its other possible uses.
-
C.
hasDominantSpecies
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
D.
hasDominantLines
Indicates that one element in a pair exhibits stronger, more prominent, or controlling linear features relative to the other.
-
E.
dominantComplex
Indicates that one entity exerts primary control, influence, or prominence over another within a given context or system.
- 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_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:12 p.m.