Triple
T29655248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warp Gate |
E750245
|
entity |
| Predicate | cooldownType |
P63769
|
FINISHED |
| Object | per-unit warp-in cooldown |
—
|
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: per-unit warp-in cooldown | Statement: [Warp Gate, cooldownType, per-unit warp-in cooldown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooldownType Context triple: [Warp Gate, cooldownType, per-unit warp-in cooldown]
-
A.
cooldown
chosen
Indicates that an entity must wait a specified period of time before performing the same action or a related action again.
-
B.
airedUntil
Indicates the date or time up to which something, typically a broadcast or series, was shown or transmitted.
-
C.
dormancyPeriod
Indicates the length of time an entity remains inactive or in a dormant state before resuming activity.
-
D.
freezeUpPeriod
Indicates a time span during which something becomes or remains frozen and unable to move or function normally.
-
E.
explosionDelay
Indicates a temporal offset between the triggering of an explosion event and the moment the explosion actually occurs.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.