Triple
T29647151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Leeds |
E756033
|
entity |
| Predicate | mostNotableHolders |
P56406
|
FINISHED |
| Object | Osborne family |
—
|
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: Osborne family | Statement: [Duke of Leeds, mostNotableHolders, Osborne family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostNotableHolders Context triple: [Duke of Leeds, mostNotableHolders, Osborne family]
-
A.
hasNotableHolders
Indicates that certain entities are recognized as prominent or distinguished bearers, owners, or occupants of another entity.
-
B.
mostNotableHolder
chosen
Indicates that one entity is the most prominent or distinguished bearer or possessor of another entity (such as a title, record, or role) compared to all other holders.
-
C.
roleOfHolders
Indicates that certain entities serve as holders or bearers of a specified role, function, or position in relation to something else.
-
D.
typicalNumberOfHolders
Indicates the usual or expected number of entities that hold or possess a given item, role, or resource.
-
E.
portfolioOftenHeldBy
Indicates that a portfolio is frequently possessed, managed, or maintained by a particular type of holder or entity.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ed3d37c81909b3e973fb9dd70cc |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:50 p.m.