Triple

T15207409
Position Surface form Disambiguated ID Type / Status
Subject Timpohon–Low’s Peak route E363423 entity
Predicate isWellEstablished P117124 FINISHED
Object true 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: true | Statement: [Timpohon–Low’s Peak route, isWellEstablished, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isWellEstablished
Context triple: [Timpohon–Low’s Peak route, isWellEstablished, true]
  • A. establishedAs
    Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
  • B. establishedTo
    Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
  • C. establishedBase
    Indicates that an entity has set up or founded a base or primary operational location in relation to another entity or place.
  • D. establishedToImplement
    Indicates that something (such as an organization, system, or structure) was created or set up for the purpose of carrying out or realizing a particular plan, policy, function, or objective.
  • E. establishedFollowing
    Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
  • F. None of above. chosen

Provenance (4 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e006b8e2788190bd1831762e4181ae completed April 15, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69deb97ee9d881908711dbe12a55283c completed April 14, 2026, 10:02 p.m.
PDg Predicate description generation batch_69dec72059c08190a34f513a00185b08 completed April 14, 2026, 11 p.m.
Created at: April 10, 2026, 3:11 a.m.