Triple
T9666368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelham-Holles |
E233714
|
entity |
| Predicate | componentSurname |
P5298
|
FINISHED |
| Object | Holles |
E423197
|
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: Holles | Statement: [Pelham-Holles, componentSurname, Holles]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holles Context triple: [Pelham-Holles, componentSurname, Holles]
-
A.
Holles
chosen
Holles is an English surname historically associated with a prominent political and aristocratic family in Britain.
-
B.
Hollein
Hollein is a German-language surname most prominently associated with Austrian architects Hans Hollein and his son Max Hollein, a leading museum director.
-
C.
Holthees
Holthees is a small village in the Dutch province of North Brabant, known for its rural character and historic church.
-
D.
Hollola
Hollola is a municipality in southern Finland, located in the Päijät-Häme region near the city of Lahti.
-
E.
Hollerich
Hollerich is a district of Luxembourg City known for its mix of residential areas, nightlife, and transport connections, including a major railway station.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3a63948190be3f48f87bdbccf1 |
completed | April 1, 2026, 10:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a1c8b188190bcff470244b21640 |
completed | April 4, 2026, 10:01 p.m. |
Created at: March 30, 2026, 8:15 p.m.