Triple
T38593188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy Pulse Rifle |
E932499
|
entity |
| Predicate | designGenre |
P200799
|
FINISHED |
| Object | sci-fi military weapon |
—
|
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: sci-fi military weapon | Statement: [Heavy Pulse Rifle, designGenre, sci-fi military weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designGenre Context triple: [Heavy Pulse Rifle, designGenre, sci-fi military weapon]
-
A.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
B.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
C.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
D.
possibleGenre
Indicates that something may belong to, be classified under, or be associated with a particular genre as one of several potential genre options.
-
E.
namedForGenre
Indicates that something is given a name based on or derived from a particular genre.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
| PDg | Predicate description generation | batch_69ffacdea2408190949dba9edeca4412 |
completed | May 9, 2026, 9:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.