Triple
T14149903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Arlay |
E350650
|
entity |
| Predicate | typeOfFeudalTenure |
P57399
|
FINISHED |
| Object | hereditary lordship |
—
|
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: hereditary lordship | Statement: [Lord of Arlay, typeOfFeudalTenure, hereditary lordship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFeudalTenure Context triple: [Lord of Arlay, typeOfFeudalTenure, hereditary lordship]
-
A.
typeOfFeudalGrant
Indicates the specific kind or category of feudal grant that characterizes the relationship between a grantor and a grantee within a feudal system.
-
B.
feudalType
chosen
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
C.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
D.
feudalRights
Indicates that one party holds traditional feudal privileges, claims, or entitlements over another party or resource within a hierarchical lord–vassal structure.
-
E.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61237ef481909374c1f68a2370b7 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:56 a.m.