Triple
T14984978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erkki |
E373676
|
entity |
| Predicate | cognateWith |
P2525
|
FINISHED |
| Object | Eero |
E76319
|
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: Eero | Statement: [Erkki, cognateWith, Eero]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eero Context triple: [Erkki, cognateWith, Eero]
-
A.
Eero
chosen
Eero is a masculine given name of Finnish origin, notably borne by the influential architect and designer Eero Saarinen.
-
B.
Eero Haapalainen
Eero Haapalainen was a Finnish socialist politician and military leader who served as the commander-in-chief of the Red Guards during the Finnish Civil War.
-
C.
Erkki
Erkki is a Finnish masculine given name commonly used as a variant of names like Eero or Erik.
-
D.
Eliel
Eliel is a masculine given name of Hebrew origin meaning "my God is God" or "God is God."
-
E.
Aaro
Aaro is a Finnish masculine given name commonly used in Finland and among Finnish speakers.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6ff4a7c8190ab7554f3a1a09b67 |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9694aa688190bbecb645c49e795e |
completed | May 9, 2026, 2:06 a.m. |
Created at: April 10, 2026, 2:52 a.m.