Triple
T1668318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brendan |
E36062
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Brendanus |
E36062
|
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: Brendanus | Statement: [Brendan, relatedName, Brendanus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brendanus Context triple: [Brendan, relatedName, Brendanus]
-
A.
Brendan
chosen
Brendan is a masculine given name of Irish origin, commonly used in English-speaking countries.
-
B.
Durkan
Durkan is a surname most notably associated with Jenny Durkan, the former mayor of Seattle and an American attorney and politician.
-
C.
Mordaunt
Mordaunt is a vengeful and fanatical antagonist in Alexandre Dumas’ d'Artagnan romances, known as the ruthless son of Milady de Winter who seeks to destroy the musketeers.
-
D.
Bertramus
Bertramus is a Latinized variant of the given name Bertram, historically used in medieval and ecclesiastical contexts.
-
E.
Gavan
Gavan is a given name, typically a variant spelling of Gavin, used as a masculine first name in English-speaking contexts.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62d1261481909a01c8fe4ff7500d |
completed | March 6, 2026, 5:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad683207b08190a86c266aaece4e98 |
completed | March 8, 2026, 12:14 p.m. |
Created at: March 4, 2026, 7:29 p.m.