Triple
T35881914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Assault Badge |
E1037532
|
entity |
| Predicate | wearerBranch |
P183941
|
FINISHED |
| Object | Heer |
—
|
NE NERFINISHED |
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: Heer | Statement: [General Assault Badge, wearerBranch, Heer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerBranch Context triple: [General Assault Badge, wearerBranch, Heer]
-
A.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
B.
wearerMust
Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
-
C.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
D.
wearerType
Indicates the type or category of entity that is intended to wear or use the associated item.
-
E.
wearableBy
Indicates that one entity is designed or suitable to be worn on the body by another entity.
- F. None of above. chosen
Provenance (4 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.