Triple
T3603720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eero Saarinen |
E76319
|
entity |
| Predicate | givenName |
P17
|
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: [Eero Saarinen, givenName, Eero]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eero Context triple: [Eero Saarinen, givenName, 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.
Aaro
Aaro is a Finnish masculine given name commonly used in Finland and among Finnish speakers.
-
D.
Antti
Antti is a Finnish given name, commonly used as a variant of the name Anton or Anthony.
-
E.
Tapio
Tapio is a Finnish masculine given name commonly associated with figures in Finnish culture, design, and mythology.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1df08a48190a4a4a20c8821b321 |
completed | March 8, 2026, 6:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4031dce448190b112ba4d5fa16ee0 |
completed | March 13, 2026, 12:29 p.m. |
Created at: March 8, 2026, 3:22 p.m.