Triple
T23203648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gen. of the Armies |
E580384
|
entity |
| Predicate | insigniaStatus |
P151336
|
FINISHED |
| Object | no standardized insignia historically prescribed |
—
|
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: no standardized insignia historically prescribed | Statement: [Gen. of the Armies, insigniaStatus, no standardized insignia historically prescribed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaStatus Context triple: [Gen. of the Armies, insigniaStatus, no standardized insignia historically prescribed]
-
A.
insigniaCenter
Indicates that one entity is positioned at or serves as the central element of another entity’s insignia or emblem.
-
B.
signageStatus
Indicates the current condition or state of a sign or signage (e.g., present, missing, damaged, or updated).
-
C.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an entity.
-
D.
insigniaCaption
Indicates the text that serves as a caption or explanatory label specifically for an insignia.
-
E.
insigniaUsedFor
Indicates that a particular insignia is employed or designated for a specific purpose, function, or use.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:07 p.m.