Triple
T32226257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Ernest Ryder |
E823210
|
entity |
| Predicate | calledToTheBarIn |
P48477
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Sir Ernest Ryder, calledToTheBarIn, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledToTheBarIn Context triple: [Sir Ernest Ryder, calledToTheBarIn, 1981]
-
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.
nominatedToCourtOn
Indicates that an entity has been formally proposed or selected for appointment to a specific court on a particular date or occasion.
-
C.
jurisdictionOfBarEligibility
Indicates the jurisdiction in which an individual is eligible or authorized to be admitted to practice law (i.e., to the bar).
-
D.
jurisdictionAdmittedToBar
Indicates that a legal professional has been formally admitted and authorized to practice law within a particular jurisdiction.
-
E.
nominatedToCourt
Indicates that one entity has been formally proposed or selected for appointment to a judicial court position.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbcbd31c8190a482a5fd5040410d |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.