Triple
T26943465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clone Force 99 |
E678576
|
entity |
| Predicate | mutation |
P68687
|
FINISHED |
| Object | enhanced marksmanship (Crosshair) |
—
|
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: enhanced marksmanship (Crosshair) | Statement: [Clone Force 99, mutation, enhanced marksmanship (Crosshair)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutation Context triple: [Clone Force 99, mutation, enhanced marksmanship (Crosshair)]
-
A.
mutationType
Indicates the specific kind or category of genetic alteration that has occurred in an entity.
-
B.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
C.
secondaryMutation
Indicates that an additional, subsequent genetic alteration has occurred following an initial mutation in the same biological context.
-
D.
mutationAssociatedWith
chosen
Indicates that a specific genetic mutation is linked or related to another entity, such as a disease, trait, or molecular effect.
-
E.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 6:20 a.m.