Triple
T32185786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PO2 |
E822104
|
entity |
| Predicate | insigniaChevronsCount |
P107045
|
FINISHED |
| Object | two chevrons |
—
|
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: two chevrons | Statement: [PO2, insigniaChevronsCount, two chevrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaChevronsCount Context triple: [PO2, insigniaChevronsCount, two chevrons]
-
A.
insigniaChevronCount
chosen
Indicates the number of chevron-shaped insignia elements associated with an entity, typically reflecting its rank or status.
-
B.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
C.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
D.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
E.
corpsInsignia
Indicates that one entity serves as the official emblem, badge, or insignia representing a particular corps or military branch associated with another entity.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6babadb3481908b49400b3ab42a7c |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.