Triple
T35592770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Çavuş |
E1028545
|
entity |
| Predicate | branchSpecificInsignia |
P176495
|
FINISHED |
| Object | land forces Çavuş insignia |
—
|
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: land forces Çavuş insignia | Statement: [Çavuş, branchSpecificInsignia, land forces Çavuş insignia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchSpecificInsignia Context triple: [Çavuş, branchSpecificInsignia, land forces Çavuş insignia]
-
A.
hasDistinctiveEmblem
Indicates that an entity possesses a unique symbol, logo, or emblem that serves to distinguish it from others.
-
B.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
C.
emblemUsedOn
Indicates that a particular emblem is applied to, displayed on, or used as a symbol on a specified object, surface, or medium.
-
D.
uniformBranchInsignia
chosen
Indicates that two entities share the same branch insignia on their uniforms, signifying affiliation with the same military or organizational branch.
-
E.
alternativeEmblems
Indicates that one emblem serves as an alternative or substitute for another emblem in representing the same entity or concept.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.