Triple

T385334
Position Surface form Disambiguated ID Type / Status
Subject Fannette Island E8767 entity
Predicate hasApproximateCoordinates P10760 FINISHED
Object 39°N, 120°W (approximate) 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: 39°N, 120°W (approximate) | Statement: [Fannette Island, hasApproximateCoordinates, 39°N, 120°W (approximate)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateCoordinates
Context triple: [Fannette Island, hasApproximateCoordinates, 39°N, 120°W (approximate)]
  • A. hasCoordinates
    Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
  • B. hasApproximateValue
    Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
  • C. hasApproximateDistanceFromEquator
    Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
  • D. hasApproximateEnd
    Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
  • E. coordinateLocation
    Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
  • 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_69a2e7f47dd08190a4e294ccbbe46cd4 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec4345a48190a413261cba4eafd7 completed Feb. 28, 2026, 1:23 p.m.
PD Predicate disambiguation batch_69a2e967d84c8190a6b647f78d95d4e4 completed Feb. 28, 2026, 1:11 p.m.
PDg Predicate description generation batch_69a2ea2dc3088190a2aeb4496aff3582 completed Feb. 28, 2026, 1:14 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.