Triple
T6724737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Montagu, 1st Baron Swaythling |
E153487
|
entity |
| Predicate | elevatedToPeerageFor |
P73370
|
FINISHED |
| Object | services to banking |
—
|
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: services to banking | Statement: [Samuel Montagu, 1st Baron Swaythling, elevatedToPeerageFor, services to banking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToPeerageFor Context triple: [Samuel Montagu, 1st Baron Swaythling, elevatedToPeerageFor, services to banking]
-
A.
dateOfElevationToPeerage
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
B.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
-
C.
conveysPeerage
Indicates that one entity formally grants or transfers a noble title or rank of peerage to another entity.
-
D.
elevatedToDuchy
Indicates that a territory, region, or domain has been formally raised in rank or status to become a duchy.
-
E.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d35134148190b49fb5c25a0f8ed4 |
completed | March 27, 2026, 6:58 p.m. |
Created at: March 27, 2026, 2:08 p.m.