Triple
T18107360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evelyn Baring, 1st Earl of Cromer |
E433378
|
entity |
| Predicate | peerageCreatedIn |
P31263
|
FINISHED |
| Object | 1901 |
—
|
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: 1901 | Statement: [Evelyn Baring, 1st Earl of Cromer, peerageCreatedIn, 1901]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peerageCreatedIn Context triple: [Evelyn Baring, 1st Earl of Cromer, peerageCreatedIn, 1901]
-
A.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
B.
peerageNumberOfCreations
Indicates the number of separate times a particular peerage title has been formally created.
-
C.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
-
D.
peerageForLife
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
-
E.
nobleTitleCreationDate
chosen
Indicates the date on which a particular noble title was formally created or granted.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbb3d408190b5fc7870bc6512f4 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.