Triple
T29647193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Leeds |
E756033
|
entity |
| Predicate | heldByFamilyFrom |
P116530
|
FINISHED |
| Object | late 17th century |
—
|
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: late 17th century | Statement: [Duke of Leeds, heldByFamilyFrom, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByFamilyFrom Context triple: [Duke of Leeds, heldByFamilyFrom, late 17th century]
-
A.
heldByFamilySince
chosen
Indicates that something has been continuously possessed or owned by the same family from a certain point in time.
-
B.
heldByFamilyBranch
Indicates that something is possessed, controlled, or maintained by a specific branch or sub-lineage of a family.
-
C.
ownsByFamily
Indicates that ownership of an entity is held collectively or primarily by a family rather than by an individual or non-family organization.
-
D.
heldByDaughterOf
Indicates that something is possessed, owned, or physically held by a person who is the daughter of another specified entity.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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.