Triple
T26912130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanderbilt family residences |
E677416
|
entity |
| Predicate | includesResidence |
P194846
|
FINISHED |
| Object | The Breakers (Newport mansion) |
—
|
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: The Breakers (Newport mansion) | Statement: [Vanderbilt family residences, includesResidence, The Breakers (Newport mansion)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesResidence Context triple: [Vanderbilt family residences, includesResidence, The Breakers (Newport mansion)]
-
A.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
B.
hasExclusiveResidence
Indicates that an entity resides in exactly one specific place and has no other concurrent residences.
-
C.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
D.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
E.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: April 27, 2026, 6:02 a.m.