Triple
T4281835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond |
E97167
|
entity |
| Predicate | hasNearbyAttraction |
P2064
|
FINISHED |
| Object | Ham House |
E237156
|
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 House | Statement: [Richmond, hasNearbyAttraction, Ham House]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ham House Context triple: [Richmond, hasNearbyAttraction, Ham House]
-
A.
Ham House
chosen
Ham House is a 17th-century Stuart mansion on the River Thames renowned for its well-preserved period interiors and formal gardens.
-
B.
Blake House
Blake House is a historic residence and notable landmark located in the City of Fairfax, Virginia.
-
C.
York House
York House is a historic wing within the St James's Palace complex in central London, traditionally associated with members of the British royal family.
-
D.
York House
York House was the former name of Bridgewater House, a grand aristocratic townhouse in central London historically associated with the British nobility.
-
E.
Hunter House
Hunter House is a historic 18th-century waterfront mansion in Newport, Rhode Island, renowned for its colonial architecture and period furnishings.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503938f481909505e0a322dd2b6c |
completed | March 12, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5b7bb0168819082a49347fdfe0997 |
completed | March 14, 2026, 7:32 p.m. |
Created at: March 12, 2026, 11:07 p.m.