Triple
T38620529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutalisk |
E936852
|
entity |
| Predicate | notableBuild |
—
|
GENERATED |
| Object | Mutalisk–Zergling composition |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuild Context triple: [Mutalisk, notableBuild, Mutalisk–Zergling composition]
-
A.
notableBuildNumber
Indicates that a particular build or version number is considered significant or noteworthy in some context.
-
B.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
C.
notableVersionType
Indicates that one version of an entity is recognized as particularly significant or noteworthy relative to other versions.
-
D.
notableDeployment
Indicates that an entity has been deployed or launched in a way that is particularly significant, prominent, or widely recognized.
-
E.
notableBranch
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
- F. None of above. chosen
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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.