Triple
T38593797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Arrow |
E932514
|
entity |
| Predicate | isOnCooldown |
P63769
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sonic Arrow, isOnCooldown, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnCooldown Context triple: [Sonic Arrow, isOnCooldown, yes]
-
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.
isBusyDuring
Indicates that an entity is occupied or engaged with some activity throughout a specified time period.
-
C.
hasFreezingPeriod
Indicates that an entity is subject to a defined time interval during which freezing (e.g., of assets, operations, or conditions) is in effect.
-
D.
isFreeToUse
Indicates that something can be used without cost, restriction, or required permission.
-
E.
canBeActivatedWithin
Indicates that one entity is capable of being activated or triggered within the spatial or temporal bounds defined by 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.