Triple
T26472288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Marlborough |
E665933
|
entity |
| Predicate | connectedEstate |
P19033
|
FINISHED |
| Object | Blenheim Palace estate |
—
|
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: Blenheim Palace estate | Statement: [Duchess of Marlborough, connectedEstate, Blenheim Palace estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedEstate Context triple: [Duchess of Marlborough, connectedEstate, Blenheim Palace estate]
-
A.
keyEstate
Indicates that an entity serves as a primary or central estate, property, or asset in relation to another entity or context.
-
B.
nearbyEstate
Indicates that one estate is located close to another estate in physical space.
-
C.
hasAssociatedEstate
chosen
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
D.
countryEstate
Indicates that a particular estate or property is located within or belongs to a specified country.
-
E.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 12:20 a.m.