Triple
T13127292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Warrant Officer 4 |
E311876
|
entity |
| Predicate | rankInsigniaElement |
P107044
|
FINISHED |
| Object | one silver bar |
—
|
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: one silver bar | Statement: [Chief Warrant Officer 4, rankInsigniaElement, one silver bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInsigniaElement Context triple: [Chief Warrant Officer 4, rankInsigniaElement, one silver bar]
-
A.
rankInsigniaDescription
chosen
Indicates the descriptive text that explains the appearance or characteristics of a rank insignia associated with an entity.
-
B.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
C.
rankInsigniaStars
Indicates the number or configuration of stars displayed on a rank insignia to denote a specific rank or level.
-
D.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
-
E.
rankStyle
Indicates the manner or criteria by which items are ordered or prioritized relative to one another.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819aac388190b59bf43cc6a49d0c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.