Triple
T20184483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alba Mons |
E492817
|
entity |
| Predicate | hasNorthernFlank |
P81612
|
FINISHED |
| Object | more extensive than southern flank |
—
|
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: more extensive than southern flank | Statement: [Alba Mons, hasNorthernFlank, more extensive than southern flank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthernFlank Context triple: [Alba Mons, hasNorthernFlank, more extensive than southern flank]
-
A.
hasFlanker
Indicates that an entity is positioned or assigned as a flanking support or protection alongside another entity.
-
B.
hasNorthFace
chosen
Indicates that something possesses a side or surface that is oriented toward the north.
-
C.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
-
D.
hasNorthNeighbor
Indicates that one entity is located directly to the north of another entity.
-
E.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
- 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.