Triple
T13117876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army 63rd Infantry Division |
E311141
|
entity |
| Predicate | insigniaSymbolism |
P56741
|
FINISHED |
| Object | flaming sword |
—
|
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: flaming sword | Statement: [U.S. Army 63rd Infantry Division, insigniaSymbolism, flaming sword]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaSymbolism Context triple: [U.S. Army 63rd Infantry Division, insigniaSymbolism, flaming sword]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
insigniaMeaning
chosen
Indicates that an insignia symbolizes or represents a particular concept, value, rank, or affiliation.
-
C.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
D.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
E.
flagDesignSymbolism
Indicates the symbolic meanings or concepts represented by elements in a flag’s design.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98182011c8190a504678affbb7787 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.