Triple

T17276710
Position Surface form Disambiguated ID Type / Status
Subject Central Java E419410 entity
Predicate contains P35 FINISHED
Object Solo E118185 NE 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: Solo | Statement: [Central Java, contains, Solo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Solo
Context triple: [Central Java, contains, Solo]
  • A. Solo chosen
    Solo is a city in Central Java, Indonesia, renowned as a major center of traditional Javanese culture and batik craftsmanship.
  • B. Solo
    Solo is a 2018 Star Wars anthology film that explores the early adventures and origins of the iconic smuggler Han Solo.
  • C. Solo
    Solo is a segment from the horror anthology film "The Turning," contributing one of its self-contained, eerie narrative episodes.
  • D. Solo
    "Solo" is a jazz piano album by Mulgrew Miller showcasing his virtuosic solo performance and sophisticated improvisational style.
  • E. Solo
    Solo is the Senegalese immigrant cab driver at the heart of the film "Goodbye Solo," whose warmth and determination drive the story’s emotional journey.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d886da626481908a14ce7830329a35 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e43326ec908190934a858c30cca880 completed April 19, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01794f6cf481909d76e3d61f9888c5 completed May 11, 2026, 6:38 a.m.
Created at: April 10, 2026, 5:40 a.m.