Triple
T29567675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Welles, 1st Viscount Welles |
E753209
|
entity |
| Predicate | parliamentarySummonsAsViscount |
P131958
|
FINISHED |
| Object | 1487 |
—
|
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: 1487 | Statement: [John Welles, 1st Viscount Welles, parliamentarySummonsAsViscount, 1487]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentarySummonsAsViscount Context triple: [John Welles, 1st Viscount Welles, parliamentarySummonsAsViscount, 1487]
-
A.
summonedToParliament
chosen
Indicates that an entity has been formally called or ordered to appear and participate in a session of a parliamentary body.
-
B.
createdViscount
Indicates that one entity granted or established the noble title of viscount for another entity.
-
C.
grantsSeatInHouseOfLords
Indicates that one entity confers or bestows a seat or membership in the House of Lords upon another entity.
-
D.
electoralLord
Indicates a relationship where one entity holds the status or role of a lord by virtue of an electoral process or selection.
-
E.
parliamentarianCommander
Indicates that one entity serves as the commanding officer or leader of a parliamentarian force associated with 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 5:54 p.m.