Triple
T32928876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Scott, 1st Earl of Eldon |
E842344
|
entity |
| Predicate | createdTitleDate |
P94738
|
FINISHED |
| Object | 1821 |
—
|
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: 1821 | Statement: [John Scott, 1st Earl of Eldon, createdTitleDate, 1821]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdTitleDate Context triple: [John Scott, 1st Earl of Eldon, createdTitleDate, 1821]
-
A.
createdTitleBy
Indicates that a title (such as a work, document, or creative piece) was created by a specific agent or creator.
-
B.
creation dates referenced in title
Indicates that the title of a work explicitly mentions or refers to the dates when the work was created.
-
C.
titleDate
chosen
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
-
D.
titleCreation
Indicates that an entity is responsible for creating, originating, or authoring the title associated with another entity.
-
E.
firstUseAsTitleDate
Indicates the date on which something was first used as a title.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:20 a.m.