Triple
T9601639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inge de Bruijn |
E231863
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Inge |
E515675
|
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: Inge | Statement: [Inge de Bruijn, givenName, Inge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inge Context triple: [Inge de Bruijn, givenName, Inge]
-
A.
Inge
chosen
Inge is a given name of Germanic origin used in various European countries for both males and females.
-
B.
Inger
Inger is a central female character in Knut Hamsun’s novel "Growth of the Soil," representing the hardships and moral complexities of rural Norwegian life.
-
C.
Ingo
Ingo is a given name most notably associated with architect James Ingo Freed, designer of the United States Holocaust Memorial Museum.
-
D.
Ingrid
Ingrid is a feminine given name of Scandinavian origin that has been borne by several notable figures, including the Swedish actress Ingrid Bergman.
-
E.
Ingeborg
Ingeborg is a feminine given name of Germanic origin, commonly used in German-speaking and Scandinavian countries.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a3a49608190ad1f65195e4d5cda |
completed | April 1, 2026, 10:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d161a993c48190974bc787fafbe793 |
completed | April 4, 2026, 7:08 p.m. |
Created at: March 30, 2026, 8:07 p.m.