Triple
T382727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial double-headed eagle of Russia |
E8714
|
entity |
| Predicate | adoptedAsStateEmblem |
P1663
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Imperial double-headed eagle of Russia, adoptedAsStateEmblem, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedAsStateEmblem Context triple: [Imperial double-headed eagle of Russia, adoptedAsStateEmblem, 15th century]
-
A.
hasNationalSymbol
Indicates that an entity possesses or is associated with an officially recognized national symbol of a country or nation.
-
B.
nationalFlag
Indicates that one entity is the official national flag representing the other entity (a country or nation).
-
C.
coatOfArms
chosen
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
D.
flagFlown
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
E.
flagshipFor
Indicates that one entity serves as the primary or leading representative example for another entity, often embodying its most important qualities or status.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec40ff8c81909306eb2dfe1512af |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.