Triple
T37183049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jane Digby |
E921248
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object |
Leonidas Theotokis
Leonidas Theotokis was the son of the famed 19th-century English aristocrat and adventurer Jane Digby, belonging to the prominent Greek Theotokis family.
|
E2223008
|
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: Leonidas Theotokis | Statement: [Jane Digby, child, Leonidas Theotokis]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Leonidas Theotokis Triple: [Jane Digby, child, Leonidas Theotokis]
Generated description
Leonidas Theotokis was the son of the famed 19th-century English aristocrat and adventurer Jane Digby, belonging to the prominent Greek Theotokis family.
Provenance (5 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb36156fe481909ef6a2f427d275b4 |
completed | May 6, 2026, 12:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a406378f3088190bc5972b9f376028f |
completed | June 27, 2026, 11:57 p.m. |
| NEDg | Description generation | batch_6a4065312e888190a413095b2612a863 |
completed | June 28, 2026, 12:05 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a40659ef09c8190bd9fb4538bdfb3b1 |
completed | June 28, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:15 p.m.