Triple
T29579377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commandos Marine |
E753531
|
entity |
| Predicate | beretInsignia |
P1617
|
FINISHED |
| Object | golden anchor with dagger |
—
|
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: golden anchor with dagger | Statement: [Commandos Marine, beretInsignia, golden anchor with dagger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beretInsignia Context triple: [Commandos Marine, beretInsignia, golden anchor with dagger]
-
A.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
B.
beretColour
Indicates that one entity has a beret whose color is specified by the other entity.
-
C.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
-
D.
hasTypeOfInsignia
chosen
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
E.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7825c08190953242afe9572940 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:05 p.m.