Triple
T30565014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Power of Three |
E777945
|
entity |
| Predicate | firstActivatedIn |
P203933
|
FINISHED |
| Object | Charmed season 1 |
E218395
|
NE 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: Charmed season 1 | Statement: [The Power of Three, firstActivatedIn, Charmed season 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstActivatedIn Context triple: [The Power of Three, firstActivatedIn, Charmed season 1]
-
A.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
B.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
C.
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.
-
D.
firstOpenedAt
Indicates the date and time at which something was initially opened for the first time.
-
E.
firstUsedInEvent
Indicates that something (such as an object, method, or concept) was used for the first time during a specified event.
- F. None of above. chosen
Provenance (5 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a02f847b9848190a9fedbc411ae0918 |
completed | May 12, 2026, 9:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2856fb3e548190914895769710cccc |
completed | June 9, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_6a02f556860c8190b2995433fa05fdd0 |
completed | May 12, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_6a02f84708488190875c7ae6e76fb998 |
completed | May 12, 2026, 9:52 a.m. |
Created at: April 29, 2026, 8:21 p.m.