Triple

T27495897
Position Surface form Disambiguated ID Type / Status
Subject Currahee Regiment E694018 entity
Predicate associatedLandmark P78460 FINISHED
Object Currahee Mountain 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: Currahee Mountain | Statement: [Currahee Regiment, associatedLandmark, Currahee Mountain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedLandmark
Context triple: [Currahee Regiment, associatedLandmark, Currahee Mountain]
  • A. includesLandmark
    Indicates that one location or area contains or encompasses a specific landmark within its boundaries.
  • B. isLandmarkFor
    Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
  • C. relatedAttraction
    Indicates that one attraction is associated with or connected to another attraction in some relevant way.
  • D. hasTouristAttractionRole
    Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
  • E. notableSiteAssociatedWith chosen
    Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
  • 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_69ef538370888190b1ddf53bb4831188 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69ffff262fac8190a26ed0577e1860bd completed May 10, 2026, 3:44 a.m.
PD Predicate disambiguation batch_69fffcad7d7c8190a4ad7bb35e33bb75 completed May 10, 2026, 3:34 a.m.
Created at: April 27, 2026, 1:08 p.m.