Triple
T21352710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuno von Westarp |
E526529
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Kuno |
—
|
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: Kuno | Statement: [Kuno von Westarp, givenName, Kuno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuno Context triple: [Kuno von Westarp, givenName, Kuno]
-
A.
Kuno
Kuno is the rebellious central character in E.M. Forster’s dystopian science fiction story "The Machine Stops," who challenges the oppressive, technology-dependent society in which he lives.
-
B.
Kuno
chosen
Kuno is a masculine given name of German origin, historically borne by various nobles and notable figures in German-speaking regions.
-
C.
Okapa
Okapa is a rural town in Papua New Guinea known for its highland culture and production of premium coffee.
-
D.
Komo
Komo is a town located in Hela Province in the Highlands region of Papua New Guinea.
-
E.
Komo
The Komo are an ethnic group indigenous to western Ethiopia, particularly associated with the Gambela Region, with their own distinct language and cultural traditions.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad34a1d48190b14fa099968faf7c |
completed | April 22, 2026, 11:12 a.m. |
Created at: April 16, 2026, 5:05 p.m.