Triple
T2797001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleet Admiral (United States Navy) |
E53059
|
entity |
| Predicate | uniformInsigniaLocation |
P4762
|
FINISHED |
| Object | shoulder boards |
—
|
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: shoulder boards | Statement: [Fleet Admiral (United States Navy), uniformInsigniaLocation, shoulder boards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniformInsigniaLocation Context triple: [Fleet Admiral (United States Navy), uniformInsigniaLocation, shoulder boards]
-
A.
hasOfficialInsigniaLocation
chosen
Indicates the specific place where an entity’s official insignia is physically located or displayed.
-
B.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
C.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
D.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
E.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf0f4988190bffc3abab7edbb81 |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.