Triple
T13484686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Armstrong-Jones, Viscount Linley |
E318464
|
entity |
| Predicate | styledAsViscountSince |
P73846
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Charles Armstrong-Jones, Viscount Linley, styledAsViscountSince, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styledAsViscountSince Context triple: [Charles Armstrong-Jones, Viscount Linley, styledAsViscountSince, 2017]
-
A.
createdViscount
Indicates that one entity granted or established the noble title of viscount for another entity.
-
B.
createdViscountIn
Indicates that an entity conferred or established the noble title of viscount in a particular place, context, or jurisdiction.
-
C.
aristocraticTitleHeldFrom
chosen
Indicates the time period or starting point from which an aristocratic title was held by an entity.
-
D.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
E.
aristocraticTitleHeldBy
Indicates that a specific aristocratic or noble title is held or borne by a particular person.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3a15b48190b63fb59e926a97ae |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.