Triple

T34723742
Position Surface form Disambiguated ID Type / Status
Subject Pollasky E1000990 entity
Predicate hasGeographicalFeatureClass P63447 FINISHED
Object populated place 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: populated place | Statement: [Pollasky, hasGeographicalFeatureClass, populated place]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGeographicalFeatureClass
Context triple: [Pollasky, hasGeographicalFeatureClass, populated place]
  • A. hasGeographyCharacteristic
    Indicates that an entity possesses a specific geographical feature, property, or attribute.
  • B. hasGeographicType
    Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
  • C. USGSFeatureClass chosen
    Indicates a classification relationship where a geographic feature is assigned a specific feature class category as defined by the U.S. Geological Survey.
  • D. physiographicClassificationBy
    Indicates a relationship where an entity is assigned a physiographic category or type according to a specified classifier, method, or authority.
  • E. isDerivedFromTopographicalFeature
    Indicates that something originates from, is based on, or is obtained from a specific topographical or geographic feature.
  • 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_69f76daeb6e48190a4c9a6b0edc80f72 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd864235b481908738dbb69556bc62 completed May 8, 2026, 6:44 a.m.
PD Predicate disambiguation batch_69fd8373b6bc819091c554f29ee17fec completed May 8, 2026, 6:32 a.m.
Created at: May 3, 2026, 3:59 p.m.