Triple
T8306277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Scott of Foscote |
E194470
|
entity |
| Predicate | createdLifePeerageDate |
P2735
|
FINISHED |
| Object | 1999-06-28 |
—
|
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: 1999-06-28 | Statement: [Lord Scott of Foscote, createdLifePeerageDate, 1999-06-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdLifePeerageDate Context triple: [Lord Scott of Foscote, createdLifePeerageDate, 1999-06-28]
-
A.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
B.
dateOfElevationToPeerage
chosen
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
C.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
D.
nobleTitleCreationDate
Indicates the date on which a particular noble title was formally created or granted.
-
E.
peerageForLife
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
- 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.