Triple
T33133138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrence Washington |
E847926
|
entity |
| Predicate | ancestralHomeAssociated |
P147258
|
FINISHED |
| Object | Sulgrave Manor |
—
|
NE NERFINISHED |
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: Sulgrave Manor | Statement: [Lawrence Washington, ancestralHomeAssociated, Sulgrave Manor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralHomeAssociated Context triple: [Lawrence Washington, ancestralHomeAssociated, Sulgrave Manor]
-
A.
ancestorHouse
Indicates that one entity is the house or dwelling associated with the ancestors of another entity.
-
B.
associatedWithHistoricHome
Indicates a relationship in which an entity is connected or linked in some relevant way to a historic home.
-
C.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
D.
hasAncestralResidence
chosen
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
E.
associatedWithHeirApparent
Indicates a relationship in which an entity is connected or linked to a designated heir apparent, typically through role, status, or relevant association.
- F. None of above.
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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:27 a.m.