Triple
T29954995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stamford estates |
E760872
|
entity |
| Predicate | isLongAssociatedWith |
P168294
|
FINISHED |
| Object | Grey family |
—
|
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: Grey family | Statement: [Stamford estates, isLongAssociatedWith, Grey family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLongAssociatedWith Context triple: [Stamford estates, isLongAssociatedWith, Grey family]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
originallyAssociatedWith
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
-
C.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
D.
endedAssociationWith
Indicates that a previously existing association or relationship between two entities has been terminated or discontinued.
-
E.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
- F. None of above. chosen
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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678397b6c8190938dd43f8f30f229 |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:27 p.m.