Triple
T20184492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alba Mons |
E492817
|
entity |
| Predicate | surfaceDominatedBy |
P47694
|
FINISHED |
| Object | lava flow fields |
—
|
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: lava flow fields | Statement: [Alba Mons, surfaceDominatedBy, lava flow fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceDominatedBy Context triple: [Alba Mons, surfaceDominatedBy, lava flow fields]
-
A.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
B.
surfaceFeatureOf
chosen
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
C.
dominatedRegion
Indicates that one entity exercises controlling power or authority over a particular geographic or conceptual region.
-
D.
nearSideDominatedBy
Indicates that the near side of an object or region is primarily influenced, controlled, or characterized by another specified entity or factor.
-
E.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668f199688190a42094cce220f6f2 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.