Triple
T30194934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenmore (historic house) |
E767600
|
entity |
| Predicate | notableRelativeAssociation |
P1481
|
FINISHED |
| Object | George Washington |
E708
|
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: George Washington | Statement: [Kenmore (historic house), notableRelativeAssociation, George Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRelativeAssociation Context triple: [Kenmore (historic house), notableRelativeAssociation, George Washington]
-
A.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
B.
notableRelativeType
Indicates the specific familial or relational role that a notable relative has in relation to the subject.
-
C.
notablyAssociatedWith
chosen
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
D.
associatedPersonNotability
Indicates that the relationship specifies the notable characteristic, achievement, or reason for prominence of the associated person.
-
E.
sharesNotableAssociationWith
Indicates a mutual, noteworthy connection or linkage between two entities that is significant enough to be recognized or highlighted.
- F. None of above.
Provenance (4 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27589a3e5c8190b7f147d244054ea6 |
completed | June 9, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:29 p.m.