Triple
T23203649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gen. of the Armies |
E580384
|
entity |
| Predicate | pershingInsignia |
P21497
|
FINISHED |
| Object | four gold stars |
—
|
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: four gold stars | Statement: [Gen. of the Armies, pershingInsignia, four gold stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pershingInsignia Context triple: [Gen. of the Armies, pershingInsignia, four gold stars]
-
A.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
B.
symbolOnInsignia
chosen
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
C.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
D.
hasDistinctiveEmblem
Indicates that an entity possesses a unique symbol, logo, or emblem that serves to distinguish it from others.
-
E.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907b3e88819088a397a99456bf77 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.