Triple

T9943236
Position Surface form Disambiguated ID Type / Status
Subject Clayton, Missouri E194133 entity
Predicate hasLandmarkFunction P43158 FINISHED
Object secondary skyline for St. Louis region 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: secondary skyline for St. Louis region | Statement: [Clayton, Missouri, hasLandmarkFunction, secondary skyline for St. Louis region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLandmarkFunction
Context triple: [Clayton, Missouri, hasLandmarkFunction, secondary skyline for St. Louis region]
  • A. isLandmarkFor chosen
    Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
  • B. hasLandmarkArea
    Indicates that a specified area is designated as the landmark area associated with a particular entity or location.
  • C. includesLandmark
    Indicates that one location or area contains or encompasses a specific landmark within its boundaries.
  • D. hasLandmarkAtEnd
    Indicates that a landmark is located at the terminal point or end of a specified path, route, or boundary.
  • E. isLocalLandmark
    Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
  • 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_69ca82e409348190a393777356b80a2a completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb6124a188190b41feadb7b2f8922 completed April 2, 2026, 12:19 a.m.
PD Predicate disambiguation batch_69cd1d9428cc81909b4b4938566d78a7 completed April 1, 2026, 1:28 p.m.
Created at: March 30, 2026, 8:45 p.m.