Triple
T15519395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Suffolk |
E368916
|
entity |
| Predicate | representationStartOfJamesCartlidge |
P118966
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [South Suffolk, representationStartOfJamesCartlidge, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representationStartOfJamesCartlidge Context triple: [South Suffolk, representationStartOfJamesCartlidge, 2015]
-
A.
roleOfJamesTheJust
Indicates that the specified role or position is held or fulfilled by James the Just.
-
B.
createdDukeOfLennoxBy
Indicates the person or authority that formally established or conferred the title of Duke of Lennox upon someone.
-
C.
createdDukeOfRichmondBy
Indicates the act by which an authority formally established or conferred the title of Duke of Richmond upon a person.
-
D.
createdDukeOfRichmondDate
Indicates the date on which the title of Duke of Richmond was created or conferred.
-
E.
createdDukeOfYorkBy
Indicates the action by which an authority or agent formally conferred or established the title of Duke of York upon a person.
- F. None of above. chosen
Provenance (4 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e040343d9c8190a7d1f197c108bd9d |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:04 a.m.