Triple

T2219014
Position Surface form Disambiguated ID Type / Status
Subject New York–Paris E48096 entity
Predicate hasApproximateGreatCircleDistance P22795 FINISHED
Object 5840 km 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: 5840 km | Statement: [New York–Paris, hasApproximateGreatCircleDistance, 5840 km]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateGreatCircleDistance
Context triple: [New York–Paris, hasApproximateGreatCircleDistance, 5840 km]
  • A. hasApproximateDistanceFromEquator
    Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
  • B. hasApproximateDistanceScale
    Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
  • C. hasApproximateCoordinates
    Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
  • D. approximateDistanceKm chosen
    Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
  • E. hasApproximateLocation
    Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
  • 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_69a88aa1ee708190862c8c378c41e9eb completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc011d50c8190b1c375cc633f8189 completed March 7, 2026, 6:05 a.m.
PD Predicate disambiguation batch_69abbdac31d8819092d17815e11921e9 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:46 p.m.