Triple
T36529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Stephen Black |
E723
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Harold |
E9958
|
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: Harold | Statement: [Harold Stephen Black, givenName, Harold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harold Context triple: [Harold Stephen Black, givenName, Harold]
-
A.
Harold
chosen
Harold is a masculine given name of Old English origin, historically borne by several notable figures including kings and modern public personalities.
-
B.
Herbert
Herbert is a masculine given name of Germanic origin that has been borne by various notable figures, including U.S. President Herbert Hoover.
-
C.
Earl
An Earl is a noble rank in the British and some European peerage systems, historically positioned below a marquess and above a viscount.
-
D.
Carl
Carl is the given name of Carl Sagan, the renowned American astronomer, science communicator, and author.
-
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_69a24acbb90881908c9f77e74034eb52 |
completed | Feb. 28, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2b8599e2c8190a593f2c00e293f9d |
completed | Feb. 28, 2026, 9:41 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.