Triple
T2872836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry House |
E56804
|
entity |
| Predicate | hasResident |
P6481
|
FINISHED |
| Object | Henry family |
E304663
|
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: Henry family | Statement: [Henry House, hasResident, Henry family]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henry family Context triple: [Henry House, hasResident, Henry family]
-
A.
Henry family
chosen
The Henry family is a lineage whose surname is associated with the historic Henry House and its heritage.
-
B.
Hall family
The Hall family is a familial group or lineage to which Sylvia Hall belongs.
-
C.
Warwick family
The Warwick family is a familial lineage or household to which Mancel Warrick belongs.
-
D.
Beaufort family
The Beaufort family was a powerful English noble lineage descended from John of Gaunt whose legitimized status and Lancastrian bloodline provided a key dynastic claim later used by Henry VII.
-
E.
Rose family
The Rose family is a prominent benefactor family whose legacy and contributions are commemorated through institutions such as the Rose Museum.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abdfe59ef88190b8bdfdd03e8965f3 |
completed | March 7, 2026, 8:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b03153b5048190925bfacc07f2db66 |
completed | March 10, 2026, 2:57 p.m. |
Created at: March 6, 2026, 10:03 p.m.