Triple
T17565296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mims Ufgood |
E427795
|
entity |
| Predicate | associatedWithCharacter |
P1481
|
FINISHED |
| Object | Sorsha |
—
|
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: Sorsha | Statement: [Mims Ufgood, associatedWithCharacter, Sorsha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sorsha Context triple: [Mims Ufgood, associatedWithCharacter, Sorsha]
-
A.
Sorsha
chosen
Sorsha is a warrior princess from the fantasy film "Willow" who initially serves her evil mother Queen Bavmorda before ultimately turning against her.
-
B.
Romeyka
Romeyka is an endangered Greek dialect spoken mainly in northeastern Turkey, notable for preserving many archaic features of Ancient Greek.
-
C.
Pelageya
Pelageya is a Russian singer renowned for her powerful folk-inspired vocals and performances that blend traditional music with contemporary styles.
-
D.
Serafima
Serafima is a feminine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Rositsa
Rositsa is a river in northern Bulgaria that serves as a significant tributary of the Yantra River.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592ce42c8190a54a0a328c5e8ffc |
completed | April 19, 2026, 4:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.