Triple
T9410319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pen Pumlumon Fawr |
E226687
|
entity |
| Predicate | hasListing |
P1278
|
FINISHED |
| Object | HuMP |
E711167
|
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: HuMP | Statement: [Pen Pumlumon Fawr, hasListing, HuMP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HuMP Context triple: [Pen Pumlumon Fawr, hasListing, HuMP]
-
A.
HuMP
chosen
HuMP is a British hill classification for summits with a topographic prominence of at least 100 metres, regardless of their absolute height.
-
B.
Hu
Hu is a common Chinese surname borne by many notable figures, including former Chinese president Hu Jintao.
-
C.
Ham
Ham is a suburban riverside district in southwest London, England, known for its historic houses, green spaces, and proximity to the River Thames.
-
D.
Ham
Ham is a small town in the Somme department of northern France, known historically for its medieval fortress and strategic location.
-
E.
Ham
Ham is a biblical figure known as one of Noah’s sons and a progenitor of several ancient peoples mentioned in the Hebrew Bible.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5255e4fc81908bf2f69c9a12ef83 |
completed | April 1, 2026, 5:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d107a5fcc081909a2d743e9673fe9e |
completed | April 4, 2026, 12:44 p.m. |
Created at: March 30, 2026, 7:47 p.m.