Triple
T18109603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy I Soter |
E433436
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Lysandra |
—
|
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: Lysandra | Statement: [Ptolemy I Soter, child, Lysandra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lysandra Context triple: [Ptolemy I Soter, child, Lysandra]
-
A.
Lysandra
chosen
Lysandra was a Hellenistic princess of the early Ptolemaic dynasty who became politically significant through her marriages into other ruling families of the era.
-
B.
Leonila
Leonila is a feminine given name commonly used in the Philippines and other Spanish-influenced cultures.
-
C.
Luciana
Luciana is a feminine given name of Latin origin, commonly used in Spanish- and Portuguese-speaking countries.
-
D.
Corinna
Corinna was an ancient Greek lyric poet from Boeotia, renowned for her choral poetry composed in the Aeolic dialect.
-
E.
Sylvana
Sylvana is a feminine given name, often considered a variant of Silvana, typically associated with meanings related to forests or woodland.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd13cb48190bff06b472e34dd0e |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:28 a.m.