Triple
T8306272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Scott of Foscote |
E194470
|
entity |
| Predicate | calledToTheBarYear |
P48477
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Lord Scott of Foscote, calledToTheBarYear, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledToTheBarYear Context triple: [Lord Scott of Foscote, calledToTheBarYear, 1959]
-
A.
calledToTheBarAt
chosen
Indicates that a person has been formally admitted and authorized to practice as a barrister by a specific legal institution or jurisdiction at a certain time.
-
B.
ordinationYear
Indicates the year in which an individual was formally ordained to a religious office or role.
-
C.
candidacyYear
Indicates the specific year in which an entity is a candidate for a position, office, award, or similar selection process.
-
D.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
-
E.
joinedInYear
Indicates that an entity became a member of, or started participating in, another entity (such as an organization, group, or institution) in a specified calendar year.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.