Triple
T16585136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Sors |
E402936
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Sors |
E1221636
|
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: Sors | Statement: [Ivan Sors, hasFamilyName, Sors]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sors Context triple: [Ivan Sors, hasFamilyName, Sors]
-
A.
Sors
chosen
Sors is a Polish surname most notably borne by the fictional character Adam Sors from the novel and film "Ashes and Diamonds."
-
B.
Sõru
Sõru is a small port village on the southern coast of Hiiumaa Island in Estonia, known for its ferry connection to the mainland and maritime setting.
-
C.
Sorso
Sorso is a town in northern Sardinia, Italy, known for its Sardinian (Sassarese) linguistic heritage and coastal Mediterranean setting.
-
D.
Sorauren
Sorauren is a village in northern Spain, near Pamplona in Navarre, known as a historic battlefield site from the Peninsular War.
-
E.
Sosruqo
Sosruqo is a fiery, trickster hero of the Caucasian Nart sagas, known for his cunning exploits and semi-divine origins.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599b057881909fcb8bbb156633a8 |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007597905881909df7dc49961b6a02 |
completed | May 10, 2026, 12:09 p.m. |
Created at: April 10, 2026, 5:16 a.m.