Triple
T18793156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Brouwer |
E459566
|
entity |
| Predicate | hasPartOfName |
P5298
|
FINISHED |
| Object | Egbertus |
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: Egbertus | Statement: [Jan Brouwer, hasPartOfName, Egbertus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Egbertus Context triple: [Jan Brouwer, hasPartOfName, Egbertus]
-
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.
Egbert of Trier
Egbert of Trier was a 10th-century Archbishop of Trier and influential patron of Ottonian art, known for commissioning important illuminated manuscripts.
-
D.
Giselbert
Giselbert is a Germanic given name of medieval origin that later evolved into the name Gilbert.
-
E.
Angilbert
Angilbert was a Frankish nobleman, poet, and churchman who served as a close advisor to Charlemagne and later became abbot of the monastery of Saint-Riquier.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59787e5988190883ed575ab4b6dec |
completed | April 20, 2026, 3:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05472071b88190a74e18be8699f0c6 |
completed | May 14, 2026, 3:53 a.m. |
Created at: April 10, 2026, 11:53 a.m.