Triple
T15047672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eaton Estate |
E379272
|
entity |
| Predicate | roleInTitle |
P38167
|
FINISHED |
| Object | principal estate of the Duke of Westminster |
—
|
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: principal estate of the Duke of Westminster | Statement: [Eaton Estate, roleInTitle, principal estate of the Duke of Westminster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTitle Context triple: [Eaton Estate, roleInTitle, principal estate of the Duke of Westminster]
-
A.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
titleOrRole
chosen
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
D.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
E.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda8e64e48190873104a02a676ff3 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.