Triple
T19299373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascraeus Mons |
E482652
|
entity |
| Predicate | flankFeature |
P20134
|
FINISHED |
| Object | radial lava flows |
—
|
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: radial lava flows | Statement: [Ascraeus Mons, flankFeature, radial lava flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flankFeature Context triple: [Ascraeus Mons, flankFeature, radial lava flows]
-
A.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
-
B.
liesOnFlankOf
chosen
Indicates that one entity is positioned along the side or lateral edge of another entity.
-
C.
allianceFlank
Indicates a cooperative maneuver where allied entities position themselves on the side of a common target or objective to gain a tactical advantage.
-
D.
spanFeature
Indicates a relationship where a feature or characteristic extends across or covers a specified span or interval.
-
E.
hasFlanker
Indicates that an entity is positioned or assigned as a flanking support or protection alongside another entity.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8852208190ba0337a9623d9bdf |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.