Triple

T35074235
Position Surface form Disambiguated ID Type / Status
Subject Apparatus Sculptoris E1011965 entity
Predicate celestialRegion P9997 FINISHED
Object region now assigned to Sculptor 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: region now assigned to Sculptor | Statement: [Apparatus Sculptoris, celestialRegion, region now assigned to Sculptor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: celestialRegion
Context triple: [Apparatus Sculptoris, celestialRegion, region now assigned to Sculptor]
  • A. solarSystemRegion
    Indicates that one entity is a region or area located within the solar system that is associated with or contains the other entity.
  • B. celestialLocation
    Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
  • C. locatedInSkyRegion chosen
    Indicates that an entity is situated within or associated with a specific region or area of the sky.
  • D. constellationType
    Indicates that one entity is classified as a specific type or category of constellation in relation to another entity.
  • E. liesBetweenConstellations
    Indicates that one entity is positioned in space such that it is located between, or bounded by, two specified constellations.
  • 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_69f76dd193108190af2528186f25b72a completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78ce78b508190955848e133398dc8 completed May 3, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69f78b8f4cc08190b49fccd798cb25d7 completed May 3, 2026, 5:53 p.m.
Created at: May 3, 2026, 4:01 p.m.