Triple
T23479227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingrid Syrstad Engen |
E570356
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Engen |
—
|
NE NERFINISHED |
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: Engen | Statement: [Ingrid Syrstad Engen, familyName, Engen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Engen Context triple: [Ingrid Syrstad Engen, familyName, Engen]
-
A.
Engen
chosen
Engen is a surname of Norwegian origin borne by various notable individuals across fields such as aviation, sports, and public service.
-
B.
Engen
Engen is a historic small town in the Hegau region of southern Germany, known for its well-preserved medieval old town and scenic volcanic landscape surroundings.
-
C.
Engern
Engern is the German name for Angria, a historical region in what is now northwestern Germany.
-
D.
Engey
Engey is a small uninhabited island in Iceland, located just off the coast of Reykjavík in Faxaflói Bay.
-
E.
Engen era
The Engen era was a Japanese historical period name (nengō) used by the Southern Court during the Nanboku-chō period in the early 14th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74e7e648190b89006dce7d7ce05 |
completed | April 29, 2026, 6:38 a.m. |
Created at: April 17, 2026, 6:02 p.m.