Triple

T65784
Position Surface form Disambiguated ID Type / Status
Subject Schwarzschild black hole E1310 entity
Predicate hasHorizonType P1972 FINISHED
Object non-rotating event horizon 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: non-rotating event horizon | Statement: [Schwarzschild black hole, hasHorizonType, non-rotating event horizon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHorizonType
Context triple: [Schwarzschild black hole, hasHorizonType, non-rotating event horizon]
  • A. hasTrailType
    Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
  • B. hasFieldOfView
    Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
  • C. hasPeakUsageInHemisphere
    Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
  • D. hasBoundaryType chosen
    Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
  • E. hasSegmentType
    Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
  • 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_69a24ba4f760819081f6638a3c70538a completed Feb. 28, 2026, 1:57 a.m.
NER Named-entity recognition batch_69a2516eda54819090f5c14384d4eab1 completed Feb. 28, 2026, 2:22 a.m.
PD Predicate disambiguation batch_69a24ea5c140819080409a968c8d2ce8 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.