Triple
T16329341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agnieszka |
E396506
|
entity |
| Predicate | cognate |
P2527
|
FINISHED |
| Object | Agneta |
E396509
|
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: Agneta | Statement: [Agnieszka, cognate, Agneta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Agneta Context triple: [Agnieszka, cognate, Agneta]
-
A.
Agneta
chosen
Agneta is a feminine given name, primarily used in Scandinavian countries, that is a variant of the name Agnes.
-
B.
Margareta
Margareta is a feminine given name used in various European languages, closely related to and derived from the name Margaret.
-
C.
Ottilia
Ottilia is a feminine given name of Germanic origin, related to Otto and typically interpreted to mean "wealth" or "prosperity."
-
D.
Gunilla
Gunilla is a Scandinavian female given name, particularly common in Sweden and other Nordic countries.
-
E.
Maddalene
Maddalene is a feminine given name, typically considered a variant of Maddalena or Magdalene, with roots in Christian and European naming traditions.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4ddc5608190b24fe2e871691470 |
completed | April 17, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00261134108190812da262b424a476 |
completed | May 10, 2026, 6:30 a.m. |
Created at: April 10, 2026, 5:07 a.m.