Triple
T16087718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Edwin Smith |
E390274
|
entity |
| Predicate | appointedLordChancellor |
P56951
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [Frederick Edwin Smith, appointedLordChancellor, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedLordChancellor Context triple: [Frederick Edwin Smith, appointedLordChancellor, 1919]
-
A.
lordChancellor
chosen
Indicates that one entity holds the position or role of Lord Chancellor in relation to another entity (such as a state, monarch, or government).
-
B.
appointedLordHighTreasurer
Indicates that one entity formally appointed another to the position of Lord High Treasurer.
-
C.
appointedAsLawLord
Indicates that an individual has been formally appointed to serve as a Law Lord (a judicial member of the House of Lords).
-
D.
appointedAsLordOfAppealInOrdinary
Indicates that a person has been formally appointed to serve in the judicial office of Lord of Appeal in Ordinary.
-
E.
appointedLordOfAppealInOrdinaryYear
Indicates the year in which an individual was appointed as a Lord of Appeal in Ordinary.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.