Triple
T16064696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LightCore Skylanders |
E389701
|
entity |
| Predicate | activatesWhen |
P103230
|
FINISHED |
| Object | placed on the Portal of Power |
—
|
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: placed on the Portal of Power | Statement: [LightCore Skylanders, activatesWhen, placed on the Portal of Power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activatesWhen Context triple: [LightCore Skylanders, activatesWhen, placed on the Portal of Power]
-
A.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
B.
activeAfter
chosen
Indicates that one entity becomes active only after another specified event, state, or time has occurred.
-
C.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
D.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
E.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.