Triple
T34958608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War with Henry VI, Holy Roman Emperor |
E1008184
|
entity |
| Predicate | primaryClaimant |
P206766
|
FINISHED |
| Object | Henry VI, Holy Roman Emperor |
E167193
|
NE 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: Henry VI, Holy Roman Emperor | Statement: [War with Henry VI, Holy Roman Emperor, primaryClaimant, Henry VI, Holy Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryClaimant Context triple: [War with Henry VI, Holy Roman Emperor, primaryClaimant, Henry VI, Holy Roman Emperor]
-
A.
formerClaimant
Indicates that an entity previously held the status of claimant in a claim or dispute but no longer does so.
-
B.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
C.
supportedClaimant
Indicates that one entity has provided assistance, backing, or advocacy in favor of another entity who is making a claim or seeking a benefit.
-
D.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
E.
primaryCase
Indicates that an entity is the main or leading instance in a set of related cases or occurrences.
- F. None of above. chosen
Provenance (5 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3803ee73348190b377b15cf93ac660 |
completed | June 21, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4 p.m.