Triple

T31690241
Position Surface form Disambiguated ID Type / Status
Subject Wilderness Road E808769 entity
Predicate barrierOvercome P159281 FINISHED
Object Appalachian Mountains 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: Appalachian Mountains | Statement: [Wilderness Road, barrierOvercome, Appalachian Mountains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: barrierOvercome
Context triple: [Wilderness Road, barrierOvercome, Appalachian Mountains]
  • A. overcomes
    Indicates that one entity successfully prevails against, defeats, or gains control over another entity or opposing force.
  • B. overcameHoldingOf
    Indicates that one entity successfully defeated, reversed, or nullified another entity’s control, possession, or dominance over something.
  • C. brokeSoundBarrier
    Indicates that an entity achieved a speed exceeding the speed of sound, thereby breaking the sound barrier.
  • D. barrierAddressed chosen
    Indicates that an identified obstacle, hindrance, or constraint affecting an entity or process has been actively dealt with, mitigated, or removed.
  • E. seeksToOvercome
    Indicates an intentional effort by one entity to defeat, surpass, or remove an obstacle, limitation, or opposing force associated with another entity or condition.
  • 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_69f348ddcbc48190950cabcc25ff29b3 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6afebd7ec8190ab696f363d84abf0 completed May 3, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69f6aca3dedc81908b519d53d2909868 completed May 3, 2026, 2:02 a.m.
Created at: April 30, 2026, 11:08 p.m.