Triple
T28311098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Combermere |
E713994
|
entity |
| Predicate | peerageCreationContext |
P164676
|
FINISHED |
| Object | Napoleonic Wars |
—
|
NE NERFINISHED |
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: Napoleonic Wars | Statement: [Viscount Combermere, peerageCreationContext, Napoleonic Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peerageCreationContext Context triple: [Viscount Combermere, peerageCreationContext, Napoleonic Wars]
-
A.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
B.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
-
C.
peerageNumberOfCreations
Indicates the number of separate times a particular peerage title has been formally created.
-
D.
peerageForLife
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
-
E.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 27, 2026, 11:40 p.m.