Triple
T3405673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aubert |
E71764
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Aubertus |
E71764
|
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: Aubertus | Statement: [Aubert, hasVariant, Aubertus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aubertus Context triple: [Aubert, hasVariant, Aubertus]
-
A.
Thaddaeus
Thaddaeus is a disciple of Jesus traditionally counted among the Twelve Apostles in Christian tradition, often identified with Jude the Apostle.
-
B.
Armandus
Armandus is a masculine given name, a Latinized variant of Armand, historically associated with European, particularly French and Dutch, usage.
-
C.
Gerhardus
Gerhardus is a masculine given name of Germanic origin, closely related to names like Gerhard and Gerard, typically meaning “strong with the spear” or “brave with the spear.”
-
D.
Bertramus
Bertramus is a Latinized variant of the given name Bertram, historically used in medieval and ecclesiastical contexts.
-
E.
Aubert
chosen
Aubert is a French given name and surname of Germanic origin, historically associated with medieval nobility and Christian saints.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8ec68c88190913df5f6cafad9e9 |
completed | March 8, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b34bd8c0ec8190bd44d33fc031c845 |
completed | March 12, 2026, 11:27 p.m. |
Created at: March 8, 2026, 3:15 p.m.