Triple
T26264505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auchincloss |
E656941
|
entity |
| Predicate | hasResidenceHistoryIn |
P192068
|
FINISHED |
| Object | Newport, Rhode Island |
—
|
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: Newport, Rhode Island | Statement: [Auchincloss, hasResidenceHistoryIn, Newport, Rhode Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidenceHistoryIn Context triple: [Auchincloss, hasResidenceHistoryIn, Newport, Rhode Island]
-
A.
hasNearbyFormerResidenceOf
Indicates that one entity is located near a place that used to be the residence of another entity.
-
B.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
C.
hasSignificantResidence
chosen
Indicates that an entity maintains an important or primary place of residence at a specified location.
-
D.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
E.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 26, 2026, 9:11 p.m.