Triple
T35726306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saunders family (local landowners) |
E1032623
|
entity |
| Predicate | hasNotableEstateIn |
P203759
|
FINISHED |
| Object | Saunderstown, Rhode Island |
E316695
|
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: Saunderstown, Rhode Island | Statement: [Saunders family (local landowners), hasNotableEstateIn, Saunderstown, Rhode Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEstateIn Context triple: [Saunders family (local landowners), hasNotableEstateIn, Saunderstown, Rhode Island]
-
A.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
B.
hasNotableHousingEstate
chosen
Indicates that a place or area contains a housing estate that is considered significant or noteworthy in some recognized way.
-
C.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
D.
hadEstates
Indicates that an entity possessed or owned one or more estates (properties or landholdings).
-
E.
nobleEstate
Indicates that an entity is a noble’s estate or property associated with nobility.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389154b69c81908454d0101174b191 |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.