Triple
T13378610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cush |
E319255
|
entity |
| Predicate | relatedBiblicalFigure |
P35021
|
FINISHED |
| Object | Ham |
E381221
|
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: [Cush, relatedBiblicalFigure, Ham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ham Context triple: [Cush, relatedBiblicalFigure, Ham]
-
A.
Ham
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 a small town in the Somme department of northern France, known historically for its medieval fortress and strategic location.
-
C.
Ham
chosen
Ham is a biblical figure known as one of Noah’s sons and a progenitor of several ancient peoples mentioned in the Hebrew Bible.
-
D.
Ham
Ham is a municipality in the Belgian province of Limburg, known for its rural character and location in the Flemish Region.
-
E.
HAM
HAM is the IATA airport code for Hamburg Airport, the international airport serving the city of Hamburg, Germany.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce56c6c8190adf4e19f6d1bc233 |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f726893a8c8190b26b5f7c7fb96f1f |
completed | May 3, 2026, 10:42 a.m. |
Created at: April 9, 2026, 9:33 p.m.