Triple
T26371988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaumont family |
E660797
|
entity |
| Predicate | heldFeudalLordship |
P117346
|
FINISHED |
| Object | Sark |
—
|
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: Sark | Statement: [Beaumont family, heldFeudalLordship, Sark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldFeudalLordship Context triple: [Beaumont family, heldFeudalLordship, Sark]
-
A.
heldFief
chosen
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
-
B.
feudalRights
Indicates that one party holds traditional feudal privileges, claims, or entitlements over another party or resource within a hierarchical lord–vassal structure.
-
C.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
D.
feud
Indicates a prolonged, mutual state of hostility or conflict between two or more parties.
-
E.
formerFiefOf
Indicates that a territory or domain was previously under the control or jurisdiction of a specified lord, ruler, or political entity as a fief.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6103043288190b762b7e1eda5a46b |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:58 p.m.