Triple

T7654300
Position Surface form Disambiguated ID Type / Status
Subject Hualālai E173336 entity
Predicate hasTopographicIsolation_km P1318 FINISHED
Object 27 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: 27 | Statement: [Hualālai, hasTopographicIsolation_km, 27]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTopographicIsolation_km
Context triple: [Hualālai, hasTopographicIsolation_km, 27]
  • A. topographicIsolation chosen
    Indicates the distance from a geographic feature to the nearest point of equal or greater elevation, expressing how isolated it is from higher terrain.
  • B. geographicIsolation
    Indicates that an entity is separated from others by physical distance or natural barriers, limiting interaction or exchange between them.
  • C. emergedAboveSeaLevel
    Indicates that something rose or became exposed above the surface of the sea from a previously submerged or lower position.
  • D. hydrologicallyIsolatedFrom
    Indicates that one water body or hydrological feature has no direct surface or subsurface water connection or exchange with another.
  • E. isolatedBy
    Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
  • 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_69c6995473348190a4f41d110d619a18 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7061cbc3c8190a917dd7e71214182 completed March 27, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69c7015dd8fc8190bc5f52a12bd46209 completed March 27, 2026, 10:14 p.m.
Created at: March 27, 2026, 3:59 p.m.