Triple
T1466891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial arms of the French Empire under Napoleon I |
E27043
|
entity |
| Predicate | mainSymbol |
P18980
|
FINISHED |
| Object | 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: eagle | Statement: [Imperial arms of the French Empire under Napoleon I, mainSymbol, eagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSymbol Context triple: [Imperial arms of the French Empire under Napoleon I, mainSymbol, eagle]
-
A.
mainCoordinateSymbol
Indicates that one symbol serves as the primary coordinate reference or anchor for positioning or aligning other related elements.
-
B.
typicalSymbol
chosen
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
C.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
D.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
E.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5bcfa0881909d6137c69825bc7a |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.