Triple
T36834338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlborough estates |
E910229
|
entity |
| Predicate | nobleFamilySeatOf |
P10501
|
FINISHED |
| Object | Dukes of Marlborough |
—
|
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: Dukes of Marlborough | Statement: [Marlborough estates, nobleFamilySeatOf, Dukes of Marlborough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleFamilySeatOf Context triple: [Marlborough estates, nobleFamilySeatOf, Dukes of Marlborough]
-
A.
nobleFamilySeat
chosen
Indicates the location that serves as the principal seat or main residence of a noble family.
-
B.
formerFamilySeat
Indicates that a location was previously the principal residence or ancestral home of a particular family but no longer holds that status.
-
C.
dynasticSeat
Indicates that a particular location serves as the principal seat of power or ruling center for a specific dynasty or ruling family.
-
D.
ethnicBaseOfRulingHouse
Indicates that a particular ethnic group forms the primary ancestral or cultural basis of a ruling house or dynasty.
-
E.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.