Triple
T36020466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iriga Volcano |
E1041966
|
entity |
| Predicate | hasFlankFeature |
P145116
|
FINISHED |
| Object | landslide scars |
—
|
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: landslide scars | Statement: [Iriga Volcano, hasFlankFeature, landslide scars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlankFeature Context triple: [Iriga Volcano, hasFlankFeature, landslide scars]
-
A.
hasFlankFeatures
chosen
Indicates that an entity possesses specific characteristics or attributes located on its sides or flanks.
-
B.
hasFrontFeature
Indicates that an entity possesses a specific characteristic, component, or attribute located on its front side.
-
C.
hasFrontLineFeature
Indicates that an entity possesses a specific characteristic or element located on its front side or leading edge.
-
D.
hasFlanker
Indicates that an entity is positioned or assigned as a flanking support or protection alongside another entity.
-
E.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ace302e08190a7ea85706d581063 |
completed | May 3, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.