Triple
T15761419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Westminster |
E382105
|
entity |
| Predicate | notableEstateConnection |
P19033
|
FINISHED |
| Object | London estates |
—
|
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: London estates | Statement: [Marquess of Westminster, notableEstateConnection, London estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEstateConnection Context triple: [Marquess of Westminster, notableEstateConnection, London estates]
-
A.
famousEstate
Indicates that an estate (such as a property, residence, or landholding) is widely known or renowned, typically due to its history, architecture, ownership, or cultural significance.
-
B.
nobleEstate
Indicates that an entity is a noble’s estate or property associated with nobility.
-
C.
hasAssociatedEstate
chosen
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
D.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
E.
hasNotablePersonConnection
Indicates that there exists a significant or noteworthy personal, professional, or historical relationship between the subject and the referenced person.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b52c548190a0ffa4493a4eb15c |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.