Triple
T9701738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlborough dukedom |
E234792
|
entity |
| Predicate | associatedWithResidenceType |
P542
|
FINISHED |
| Object | country house |
—
|
LITERAL 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: country house | Statement: [Marlborough dukedom, associatedWithResidenceType, country house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithResidenceType Context triple: [Marlborough dukedom, associatedWithResidenceType, country house]
-
A.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
B.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
C.
residenceStatus
Indicates the type or condition of an entity’s living arrangement or place of residence in relation to a specified location.
-
D.
residencyPattern
Indicates the typical way an entity resides or occupies a place over time, such as its usual location, duration, or frequency of stay.
-
E.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d70f55c8190934f37c25e9d4ba4 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.