Triple

T528048
Position Surface form Disambiguated ID Type / Status
Subject Lysgårdsbakken E10966 entity
Predicate hasKPoint P15212 FINISHED
Object K-123 (large hill) 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: K-123 (large hill) | Statement: [Lysgårdsbakken, hasKPoint, K-123 (large hill)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKPoint
Context triple: [Lysgårdsbakken, hasKPoint, K-123 (large hill)]
  • A. hasNumberOfPoints
    Indicates that an entity is associated with a specific count of points it possesses or comprises.
  • B. hasHelpPoint
    Indicates that one entity provides or contains a designated help or assistance point for another entity.
  • C. hasPar
    Indicates a relationship where one entity has another entity as its parent.
  • D. hasCP
    Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
  • E. hasKeel
    Indicates that an entity possesses a keel as a structural or anatomical feature.
  • 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_69a2e84b16c4819088d284c47c3a7968 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f1d2851c81908129f7da932ab7b3 completed Feb. 28, 2026, 1:46 p.m.
PD Predicate disambiguation batch_69a2f01ac3ec8190a94a05955532c7fa completed Feb. 28, 2026, 1:39 p.m.
PDg Predicate description generation batch_69a2f0dcff1881909c18e8c599c150a1 completed Feb. 28, 2026, 1:42 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.