Triple

T17121239
Position Surface form Disambiguated ID Type / Status
Subject Kármán line E415469 entity
Predicate hasLayerRelation P33476 FINISHED
Object near the boundary of the mesosphere and thermosphere 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: near the boundary of the mesosphere and thermosphere | Statement: [Kármán line, hasLayerRelation, near the boundary of the mesosphere and thermosphere]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLayerRelation
Context triple: [Kármán line, hasLayerRelation, near the boundary of the mesosphere and thermosphere]
  • A. hasRelation chosen
    Indicates that there exists some specified relationship or association between two entities.
  • B. hasLayerFunction
    Indicates that one entity serves as the functional role or operational purpose of a specific layer within another entity or system.
  • C. hasPhaseRelation
    Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
  • D. hasKeyRelationship
    Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
  • E. hasRelationships
    Indicates that an entity is connected to one or more other entities through specified types of relationships.
  • 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_69d886d090cc8190a39cb94992586905 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3e809ee888190a2cf69d59c0b9c20 completed April 18, 2026, 8:22 p.m.
PD Predicate disambiguation batch_69e35d6d20808190a38bb32e2294bc48 completed April 18, 2026, 10:31 a.m.
Created at: April 10, 2026, 5:36 a.m.