Triple
T35078476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barons Clonbrock |
E1012367
|
entity |
| Predicate | landownershipStatus |
P41739
|
FINISHED |
| Object | large landowners |
—
|
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 landowners | Statement: [Barons Clonbrock, landownershipStatus, large landowners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landownershipStatus Context triple: [Barons Clonbrock, landownershipStatus, large landowners]
-
A.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
B.
ownedLandBy
Indicates that one entity possesses legal or recognized ownership rights over a piece or area of land associated with another entity.
-
C.
hasLandStatus
chosen
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
D.
landholderIn
Indicates that one entity holds legal or recognized ownership or tenancy rights over land located within the jurisdiction or bounds of another entity.
-
E.
landholdings
Indicates the extent or collection of land owned, controlled, or held by an 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.