Triple
T15684113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Nemanja |
E380150
|
entity |
| Predicate | monasticName |
P50298
|
FINISHED |
| Object | Simeon |
E380151
|
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: Simeon | Statement: [Stefan Nemanja, monasticName, Simeon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Simeon Context triple: [Stefan Nemanja, monasticName, Simeon]
-
A.
Simeon
Simeon was a 14th-century Grand Prince of Moscow and Vladimir who helped consolidate Muscovite power in medieval Russia.
-
B.
Simeon
Simeon is a biblical figure, one of the twelve sons of Jacob and a progenitor of one of the tribes of Israel.
-
C.
Simeon
chosen
Simeon is a monastic name referring to Saint Simeon the Myrrh-streaming, a revered Orthodox Christian saint known for the miraculous flow of myrrh from his relics.
-
D.
Simeon
Simeon is a person known primarily as the child of the singer Nena.
-
E.
Simeon
Simeon is the given name of Simeon II, the last reigning Tsar of Bulgaria who later served as the country’s prime minister.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f31b5b881908e46ecd9fc6048ab |
completed | April 16, 2026, 2:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6ee4c8688190ae2fefb56171161a |
completed | May 9, 2026, 5:29 p.m. |
Created at: April 10, 2026, 4:43 a.m.