Triple
T38875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbert |
E769
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Herbertus |
E769
|
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: Herbertus | Statement: [Herbert, hasVariant, Herbertus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Herbertus Context triple: [Herbert, hasVariant, Herbertus]
-
A.
Herbert
chosen
Herbert is a masculine given name of Germanic origin that has been borne by various notable figures, including U.S. President Herbert Hoover.
-
B.
Theodor
Theodor "Ted" Nelson is an American pioneer of information technology best known for coining the term "hypertext" and envisioning global hyperlinked document systems.
-
C.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
D.
Andreas
Andreas is a masculine given name of Greek origin, commonly used in various European and international cultures.
-
E.
Edwin
Edwin is a masculine given name of Old English origin meaning "rich friend" or "prosperous friend."
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24acd14b48190b80d4329621583df |
completed | Feb. 28, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a29e420aa0819085d796612c24bcac |
completed | Feb. 28, 2026, 7:50 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.