Triple
T32977241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archduke Ferdinand Karl of Austria |
E843697
|
entity |
| Predicate | usedNameAfterRenunciation |
P175453
|
FINISHED |
| Object | Ferdinand Burg |
—
|
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: Ferdinand Burg | Statement: [Archduke Ferdinand Karl of Austria, usedNameAfterRenunciation, Ferdinand Burg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedNameAfterRenunciation Context triple: [Archduke Ferdinand Karl of Austria, usedNameAfterRenunciation, Ferdinand Burg]
-
A.
meetsBeforeRenunciation
Indicates that one entity meets another at some time prior to a specified act of renunciation by one of them.
-
B.
renouncedBy
Indicates that an entity has been formally rejected, disowned, or given up by another entity.
-
C.
tookRenunciationName
Indicates that an entity adopted a new religious or spiritual renunciation name, typically upon entering a monastic or ascetic life.
-
D.
viewOnRenunciation
Indicates a stance or perspective that an entity holds regarding the act or principle of renunciation.
-
E.
reasonForRenunciation
Indicates the specific cause, motive, or circumstance that led an entity to renounce or give up something.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:22 a.m.