Triple
T2811099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darvin Ham |
E54171
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ham |
E172209
|
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: Ham | Statement: [Darvin Ham, familyName, Ham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ham Context triple: [Darvin Ham, familyName, Ham]
-
A.
Ham
chosen
Ham is a suburban riverside district in southwest London, England, known for its historic houses, green spaces, and proximity to the River Thames.
-
B.
HAM
HAM is the IATA airport code for Hamburg Airport, the international airport serving the city of Hamburg, Germany.
-
C.
HAM
HAM is the standard abbreviation used for the Canadian Football League team, the Hamilton Tiger-Cats.
-
D.
Ho
Ho are an indigenous Adivasi community of eastern India, primarily inhabiting parts of Jharkhand and Odisha, known for their Austroasiatic Ho language and distinct cultural traditions.
-
E.
Hap
Hap is the nickname of Henry "Hap" Arnold, a pioneering U.S. Army Air Forces general and key architect of American air power during World War II.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde354a5881908cd3d545f7dda81c |
completed | March 7, 2026, 8:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce9a76388190a5dce756de2eb59f |
completed | March 10, 2026, 7:56 a.m. |
Created at: March 6, 2026, 9:59 p.m.