Triple
T32681056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich (VII.) von Hohenstaufen |
E835583
|
entity |
| Predicate | heldTitleEnd |
P11030
|
FINISHED |
| Object | 1235 |
—
|
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: 1235 | Statement: [Heinrich (VII.) von Hohenstaufen, heldTitleEnd, 1235]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTitleEnd Context triple: [Heinrich (VII.) von Hohenstaufen, heldTitleEnd, 1235]
-
A.
heldTitleFrom
Indicates that an entity possessed or held a particular title starting from a specified point in time.
-
B.
heldTitleUntil
chosen
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
C.
heldTitleUnder
Indicates that one entity possessed or occupied a particular title, rank, or office under the authority, jurisdiction, or auspices of another entity.
-
D.
heldByEnd
Indicates that an object or item is being held or supported specifically at one of its ends by an agent or another object.
-
E.
titleHeldAfter
Indicates that one entity held a particular title or position after another entity, establishing a temporal succession in holding that title.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:09 a.m.