Triple
T29567674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Welles, 1st Viscount Welles |
E753209
|
entity |
| Predicate | creationOfViscountcy |
P78853
|
FINISHED |
| Object | 1486 |
—
|
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: 1486 | Statement: [John Welles, 1st Viscount Welles, creationOfViscountcy, 1486]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationOfViscountcy Context triple: [John Welles, 1st Viscount Welles, creationOfViscountcy, 1486]
-
A.
createdViscount
chosen
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.
lordshipCreated
Indicates that a lordship was formally established or brought into existence.
-
D.
createdEarlOfWestmorlandBy
Indicates that a person or authority conferred or established the title "Earl of Westmorland" upon a specific individual.
-
E.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 28, 2026, 5:54 p.m.