Triple
T6715503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joaquim |
E153256
|
entity |
| Predicate | derivedFrom |
P909
|
FINISHED |
| Object | Saint Joachim |
E26590
|
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: Saint Joachim | Statement: [Joaquim, derivedFrom, Saint Joachim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saint Joachim Context triple: [Joaquim, derivedFrom, Saint Joachim]
-
A.
Saint Joachim
chosen
Saint Joachim is venerated in Christian tradition as the father of the Virgin Mary and the husband of Saint Anne.
-
B.
Saint Joseph
Saint Joseph is a key figure in Christianity, venerated as the earthly father of Jesus and a model of humility, obedience, and protective care.
-
C.
Simeon
Simeon is a biblical figure, one of the twelve sons of Jacob and a progenitor of one of the tribes of Israel.
-
D.
Simeon
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.
-
E.
Aloysius
Aloysius is a masculine given name of Latinized form, historically borne by several saints and used in various European languages.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1246b748190aed94e8ab8625f7e |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70096e05c8190abfa90996db37eeb |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:07 p.m.