Triple
T2143147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Master Sergeant (USSF enlisted rank) |
E47004
|
entity |
| Predicate | serviceBranchInsigniaElement |
P21497
|
FINISHED |
| Object | globe |
—
|
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: globe | Statement: [Chief Master Sergeant (USSF enlisted rank), serviceBranchInsigniaElement, globe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchInsigniaElement Context triple: [Chief Master Sergeant (USSF enlisted rank), serviceBranchInsigniaElement, globe]
-
A.
symbolOnInsignia
chosen
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
B.
serviceBranchColor
Indicates the specific color associated with a particular branch of service (e.g., military or organizational branch) as its identifying or representative color.
-
C.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
D.
serviceBrand
Indicates that one entity is the brand under which a particular service is offered or marketed by another entity.
-
E.
liveryFeature
Indicates a characteristic or design element that is part of a specific livery or external appearance scheme.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.