Triple
T5854241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie |
E130110
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Sophia |
E390085
|
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: Sophia | Statement: [Sophie, hasVariant, Sophia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sophia Context triple: [Sophie, hasVariant, Sophia]
-
A.
Sophia
Sophia of the Palatinate was a 17th-century German princess and Electress of Hanover, best known as the mother of King George I of Great Britain and a key figure in the Protestant succession to the British throne.
-
B.
Sophia
Sophia is a philosophical and theological concept signifying divine wisdom, often personified and associated with the rational principle of the cosmos.
-
C.
Sophia
Sophia is a small town located in Raleigh County in the southern part of West Virginia, United States.
-
D.
Sophia
chosen
Sophia is a feminine given name of Greek origin meaning "wisdom," widely used across many cultures and languages.
-
E.
Sophia
Sophia is a person whose given name is used in the full name Sophia Chew Nicklin Dallas.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c035529cf88190acc547ae839950e7 |
completed | March 22, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e369ce248190af33d7c09ee10af6 |
completed | March 23, 2026, 6:53 a.m. |
Created at: March 22, 2026, 3:55 p.m.