Triple
T20052074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan Fairfax, 8th Lord Fairfax of Cameron |
E499225
|
entity |
| Predicate | legalStatusOfTitle |
P114695
|
FINISHED |
| Object | hereditary peerage |
—
|
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 peerage | Statement: [Bryan Fairfax, 8th Lord Fairfax of Cameron, legalStatusOfTitle, hereditary peerage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfTitle Context triple: [Bryan Fairfax, 8th Lord Fairfax of Cameron, legalStatusOfTitle, hereditary peerage]
-
A.
hasTitleInLaw
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
-
B.
legalStatusInPlot
Indicates the legal standing or rights an entity holds within the context of a specific plot or storyline.
-
C.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
-
D.
natureOfTitle
chosen
Indicates the specific type or character of a title in relation to the entity it is associated with.
-
E.
legalCodeStatus
Indicates the legal or regulatory status assigned to a specific code within a legal or statutory system (e.g., active, repealed, pending).
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632ee4d48190b9de3a1efa064492 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.