Triple
T8717513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O-10 |
E206931
|
entity |
| Predicate | serviceBranchVariation |
P29506
|
FINISHED |
| Object | insignia design differs by service |
—
|
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: insignia design differs by service | Statement: [O-10, serviceBranchVariation, insignia design differs by service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchVariation Context triple: [O-10, serviceBranchVariation, insignia design differs by service]
-
A.
serviceBranchOptions
Indicates the available branches or divisions of service that can be selected or associated with an entity.
-
B.
serviceBranchSpecific
chosen
Indicates that something is restricted or tailored to a particular branch of service rather than being common across all branches.
-
C.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
D.
serviceBranchLevel
Indicates the hierarchical level or tier within a service branch at which an entity operates or is classified.
-
E.
hasServiceVariations
Indicates that a service is offered in multiple distinct versions, options, or configurations that differ in some defined characteristics.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cdac6988190b9f9cc1f350aae53 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.