Triple
T5831851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophia of Mecklenburg-Güstrow |
E129368
|
entity |
| Predicate | givenName |
P17
|
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: [Sophia of Mecklenburg-Güstrow, givenName, Sophia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sophia Context triple: [Sophia of Mecklenburg-Güstrow, givenName, Sophia]
-
A.
Sophia
Sophia is a philosophical and theological concept signifying divine wisdom, often personified and associated with the rational principle of the cosmos.
-
B.
Sophia
Sophia is a person whose given name is used in the full name Sophia Chew Nicklin Dallas.
-
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 was a prominent Byzantine empress of the Justinian dynasty, known for her political influence and role in imperial court affairs during the 6th century.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0346c331c8190bac050d425961485 |
completed | March 22, 2026, 6:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a19010008190af5600a035246c1a |
completed | March 23, 2026, 2:12 a.m. |
Created at: March 22, 2026, 3:54 p.m.