Triple

T3886034
Position Surface form Disambiguated ID Type / Status
Subject 944 Hidalgo E92942 entity
Predicate crossesPlanetaryRegion P13729 FINISHED
Object inner Solar System 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: inner Solar System | Statement: [944 Hidalgo, crossesPlanetaryRegion, inner Solar System]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crossesPlanetaryRegion
Context triple: [944 Hidalgo, crossesPlanetaryRegion, inner Solar System]
  • A. crossesRegion chosen
    Indicates that an entity moves through or passes across the spatial extent of a specified region.
  • B. crossedKarmanLine
    Indicates that an entity has passed beyond the Kármán line, the commonly accepted boundary between Earth's atmosphere and outer space.
  • C. crossesBorderOf
    Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
  • D. crossesBetween
    Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
  • E. crossingOf
    Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
  • 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_69aed9697de0819087c2559295ff3d12 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeec942bfc8190a398fe370715a28b completed March 9, 2026, 3:51 p.m.
PD Predicate disambiguation batch_69aee759609c8190985e96ec6d96dedd completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:20 p.m.