Triple
T36594118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ePACT |
E902749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CLARITY system variant |
C63959
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: CLARITY system variant Context triple: [ePACT, instanceOf, CLARITY system variant]
-
A.
variant of CLARITY
chosen
A variant of CLARITY is a tissue-clearing method derived from the original CLARITY protocol that modifies its chemistry or processing steps to improve transparency, antigen preservation, imaging depth, or compatibility with specific tissues or labeling techniques.
-
B.
M936 variant
The M936 variant is a specialized configuration or version of the M936 platform, distinguished by modified components or capabilities tailored for specific operational requirements.
-
C.
Replicator variant
A Replicator variant is a specialized form of self-replicating entity that diverges from a standard replicator design through altered replication mechanisms, behaviors, or constraints to achieve distinct functional or evolutionary outcomes.
-
D.
Barracuda product line variant
A Barracuda product line variant is a specific configuration or version of the Barracuda product tailored to distinct market segments, feature sets, or performance requirements within the overall product family.
-
E.
MD 500 series variant
A specific model within the MD 500 series family of light utility helicopters, distinguished by particular performance, configuration, or equipment characteristics.
- F. None of above.
Provenance (1 batch)
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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.