Triple
T34278493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick the Fair |
E879526
|
entity |
| Predicate | titleContestedWith |
P5850
|
FINISHED |
| Object | Louis IV, Holy Roman Emperor |
—
|
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: Louis IV, Holy Roman Emperor | Statement: [Frederick the Fair, titleContestedWith, Louis IV, Holy Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleContestedWith Context triple: [Frederick the Fair, titleContestedWith, Louis IV, Holy Roman Emperor]
-
A.
titleContestedIn
Indicates that a particular title or championship is being challenged or competed for within a specific event, match, or context.
-
B.
titleContested
chosen
Indicates that the legitimacy or ownership of a title is disputed between parties.
-
C.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
D.
titleContenders
Indicates that the related entities are competing or in strong contention for a particular title or championship.
-
E.
contestedAs
Indicates that one entity challenges, disputes, or competes for the status, claim, or position held by 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 1, 2026, 1:57 a.m.