Triple

T6396959
Position Surface form Disambiguated ID Type / Status
Subject anti-de Sitter space E143964 entity
Predicate hasConformalBoundaryType P1972 FINISHED
Object timelike boundary 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: timelike boundary | Statement: [anti-de Sitter space, hasConformalBoundaryType, timelike boundary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConformalBoundaryType
Context triple: [anti-de Sitter space, hasConformalBoundaryType, timelike boundary]
  • A. hasBoundaryType chosen
    Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
  • B. hasBoundaryCriterion
    Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
  • C. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • D. hasBoundarySystem
    Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
  • E. hadBorderType
    Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
  • 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_69c008db906c819096f3597d55d95432 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c068953968819083a94f5de3e11819 completed March 22, 2026, 10:09 p.m.
PD Predicate disambiguation batch_69c060f25c088190b433f78553ff1d84 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:35 p.m.