Triple
T17795707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Hamilton, 7th Duke of Abercorn |
E444284
|
entity |
| Predicate | typeOfLandowner |
P34249
|
FINISHED |
| Object | large estate holder |
—
|
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: large estate holder | Statement: [James Hamilton, 7th Duke of Abercorn, typeOfLandowner, large estate holder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLandowner Context triple: [James Hamilton, 7th Duke of Abercorn, typeOfLandowner, large estate holder]
-
A.
majorLandowner
Indicates that one entity owns a large or dominant portion of land in relation to another entity or area.
-
B.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
C.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
-
D.
landTenure
chosen
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
E.
landholderIn
Indicates that one entity holds legal or recognized ownership or tenancy rights over land located within the jurisdiction or bounds of another 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fafc2c8190b28e791267c47e3c |
completed | April 19, 2026, 7:44 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.