Triple
T5668846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. 9th Infantry Regiment |
E124921
|
entity |
| Predicate | regimentalInsigniaSymbol |
P32838
|
FINISHED |
| Object | Chinese dragon |
—
|
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: Chinese dragon | Statement: [U.S. 9th Infantry Regiment, regimentalInsigniaSymbol, Chinese dragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalInsigniaSymbol Context triple: [U.S. 9th Infantry Regiment, regimentalInsigniaSymbol, Chinese dragon]
-
A.
heraldicDivision
Indicates the way a heraldic shield or field is partitioned into distinct sections or areas.
-
B.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
C.
heraldicCharge
chosen
Indicates that one entity serves as a heraldic charge, i.e., a symbolic figure or emblem placed on another entity’s coat of arms or shield.
-
D.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
E.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.