Triple

T18298501
Position Surface form Disambiguated ID Type / Status
Subject Known Space E438294 entity
Predicate hasFictionalLocation P21117 FINISHED
Object Sol system NE NERFINISHED

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: Sol system | Statement: [Known Space, hasFictionalLocation, Sol system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sol system
Context triple: [Known Space, hasFictionalLocation, Sol system]
  • A. Sistema
    Sistema is a consumer food storage and kitchenware brand known for its reusable plastic containers and lunch solutions.
  • B. SOL
    SOL is the ICAO airline designator assigned to Solomon Airlines, the national carrier of the Solomon Islands.
  • C. SOL
    SOL is the National Rail station code for Solihull railway station in the West Midlands, England.
  • D. Sol chosen
    Sol is the Sun, the G-type main-sequence star at the center of our solar system that provides Earth with light and heat.
  • E. Sol
    Sol is a major central square and transport hub in Madrid, Spain, known as one of the city's busiest public spaces and a symbolic heart of the capital.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5017d96588190ac1e326803142976 completed April 19, 2026, 4:23 p.m.
Created at: April 10, 2026, 10:35 a.m.