Triple
T10385385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial eagle of the Holy Roman Empire |
E244745
|
entity |
| Predicate | laterVariant |
P47516
|
FINISHED |
| Object | double-headed imperial eagle |
—
|
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: double-headed imperial eagle | Statement: [Imperial eagle of the Holy Roman Empire, laterVariant, double-headed imperial eagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterVariant Context triple: [Imperial eagle of the Holy Roman Empire, laterVariant, double-headed imperial eagle]
-
A.
laterVersion
chosen
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
B.
laterVariantRole
Indicates that one role is a subsequent or later variant of another, reflecting a modified or evolved version of the original role.
-
C.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
-
D.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
E.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a42e748190b10fa7b4ca006bad |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.