Triple
T35881937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Assault Badge |
E1037532
|
entity |
| Predicate | reverseAttachment |
P93025
|
FINISHED |
| Object | vertical pin |
—
|
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: vertical pin | Statement: [General Assault Badge, reverseAttachment, vertical pin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseAttachment Context triple: [General Assault Badge, reverseAttachment, vertical pin]
-
A.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
B.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
C.
attachmentType
chosen
Indicates the specific kind or category of attachment that relates one entity to another.
-
D.
supportsAttachmentTo
Indicates that one entity provides a structural or functional basis for another entity to be attached or affixed to it.
-
E.
alsoReveres
Indicates that one entity holds reverence or deep respect for something or someone that another entity also reveres.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.