Triple
T1028624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guido |
E22196
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Wido |
E146517
|
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: Wido | Statement: [Guido, hasCognate, Wido]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wido Context triple: [Guido, hasCognate, Wido]
-
A.
Wido
chosen
Wido is a given name that functions as a variant form of the name Guido, used in various European languages.
-
B.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
C.
Otto
Otto is the title of one of the early nominative reports that were later incorporated into the official United States Reports, documenting decisions of the U.S. Supreme Court.
-
D.
Otto
Otto is the central German soldier protagonist in the 1993 war film "Stalingrad," whose experiences depict the brutality and futility of the Eastern Front in World War II.
-
E.
Otto
Otto is a given name of Germanic origin commonly used across various European 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f84c888190b5b9e44c7edb508f |
completed | March 1, 2026, 10:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acbad55a4c8190977e8e5d313c56df |
completed | March 7, 2026, 11:55 p.m. |
Created at: March 1, 2026, 7:41 p.m.