Triple

T35800933
Position Surface form Disambiguated ID Type / Status
Subject Mount Empung E1034974 entity
Predicate formsTwinComplexWith P102611 FINISHED
Object Mount Lokon NE NERFINISHED

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: Mount Lokon | Statement: [Mount Empung, formsTwinComplexWith, Mount Lokon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formsTwinComplexWith
Context triple: [Mount Empung, formsTwinComplexWith, Mount Lokon]
  • A. twinning chosen
    Indicates that two entities are paired or linked as twins, typically sharing a formally recognized, parallel, or closely matched relationship.
  • B. twinType
    Indicates that one entity is classified as a specific type or category of twin in relation to another entity.
  • C. hasTwinStructureWith
    Indicates that two entities share an identical or nearly identical structural form, typically as corresponding or mirrored counterparts.
  • D. formsWeakDoubletWith
    Indicates that one entity forms a weakly interacting or loosely coupled pair (doublet) with another entity, typically in contrast to a stronger or more tightly bound association.
  • E. formsWith
    Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
  • 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_69f76e169bd081909f16cd8c9ee7870c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fd35d108908190b79b1e8e6bbd62aa completed May 8, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69fd34cb46108190b43c3b7f67ec4cd4 completed May 8, 2026, 12:56 a.m.
Created at: May 3, 2026, 4:06 p.m.