Triple
T35348360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Council and Session |
E1020804
|
entity |
| Predicate | usesJudicialTitle |
P10405
|
FINISHED |
| Object | Lord [judicial title] |
—
|
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: Lord [judicial title] | Statement: [Lords of Council and Session, usesJudicialTitle, Lord [judicial title]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesJudicialTitle Context triple: [Lords of Council and Session, usesJudicialTitle, Lord [judicial title]]
-
A.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
B.
usesTitle
chosen
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
C.
hasJuryTitle
Indicates that an entity holds or is assigned a specific title or role as a member of a jury.
-
D.
hasTitleInLaw
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
-
E.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.