Triple
T11014076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bert Williams |
E260317
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Egbert |
E833760
|
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: Egbert | Statement: [Bert Williams, givenName, Egbert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Egbert Context triple: [Bert Williams, givenName, Egbert]
-
A.
Egbert
Egbert is a small community in Wyoming, United States.
-
B.
Egbert
chosen
Egbert was a 9th-century king of Wessex who significantly expanded West Saxon power and laid foundations for the later unification of England.
-
C.
Zwentibold
Zwentibold was a late 9th-century Carolingian king who ruled Lotharingia and was the illegitimate son of Emperor Arnulf of Carinthia.
-
D.
Adalwolf
Adalwolf is a Germanic given name meaning "noble wolf," from which the name Adolf is derived.
-
E.
Giselbert
Giselbert is a Germanic given name of medieval origin that later evolved into the name Gilbert.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a49f648190a5144625d09dec6f |
completed | April 9, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e374c238ac81908e0a5eff958d6545 |
completed | April 18, 2026, 12:10 p.m. |
Created at: April 8, 2026, 9:25 p.m.