Triple
T3285809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaritan revolver |
E68977
|
entity |
| Predicate | visualTrademark |
P47719
|
FINISHED |
| Object | massive barrel |
—
|
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: massive barrel | Statement: [Samaritan revolver, visualTrademark, massive barrel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualTrademark Context triple: [Samaritan revolver, visualTrademark, massive barrel]
-
A.
trademark
Indicates that one entity legally owns and uses a distinctive sign, name, or symbol to identify and distinguish its goods or services from those of others.
-
B.
visualIdentityDesigner
Indicates that an entity is responsible for creating or shaping the visual identity or visual branding of another entity.
-
C.
logoUsedIn
Indicates that a particular logo is employed or displayed within a specified context, medium, or artifact.
-
D.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
E.
symbolDesigned
Indicates that one entity created or planned the design of a symbolic representation (such as a logo, icon, or emblem) for 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03918c48190987d7cfd3bda9716 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.