Triple
T10997125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Björn Andrésen |
E259903
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Andrésen |
E753925
|
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: Andrésen | Statement: [Björn Andrésen, familyName, Andrésen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Andrésen Context triple: [Björn Andrésen, familyName, Andrésen]
-
A.
Andresen
chosen
Andresen is a surname of Scandinavian origin, commonly used as a variant spelling of Andersen.
-
B.
Andries
Andries is a Dutch given name traditionally used for men, equivalent to Andrew in English.
-
C.
Ascherson
Ascherson is a surname most notably associated with British actress Renée Asherson.
-
D.
Andrus
Andrus is a surname most notably associated with Cecil D. Andrus, a prominent American politician and former U.S. Secretary of the Interior.
-
E.
Count Andrenyi
Count Andrenyi is a fictional Hungarian nobleman and one of the key suspects in Agatha Christie's classic Hercule Poirot detective novel "Murder on the Orient Express."
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d20b448190958331705de3a9be |
completed | April 9, 2026, 12:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3452420c08190b9c91a9c8a807670 |
completed | April 18, 2026, 8:47 a.m. |
Created at: April 8, 2026, 9:24 p.m.