Triple
T17972791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemming Ørnskov |
E449388
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Flemming |
—
|
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: Flemming | Statement: [Flemming Ørnskov, givenName, Flemming]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flemming Context triple: [Flemming Ørnskov, givenName, Flemming]
-
A.
Flemming
chosen
Flemming is a surname and given name of Germanic origin, used by various notable individuals across fields such as politics, arts, and science.
-
B.
Krogh
Krogh is a Norwegian surname borne by various notable figures in politics, science, and the arts.
-
C.
Reinholdt
Reinholdt is a masculine given name of Germanic origin, often associated with individuals from German-speaking regions.
-
D.
Meyerhof
Meyerhof is a surname of German origin, notably borne by biochemist Otto Fritz Meyerhof, a Nobel laureate recognized for his work on muscle metabolism.
-
E.
Thomsen
Thomsen is a Danish surname commonly borne by individuals of Scandinavian origin.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fca04481908f0dd875953fd82f |
completed | April 19, 2026, 10:44 a.m. |
Created at: April 10, 2026, 10:22 a.m.