Triple
T30565015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Power of Three |
E777945
|
entity |
| Predicate | firstActivatedBy |
P27625
|
FINISHED |
| Object | Prue Halliwell |
E777941
|
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: Prue Halliwell | Statement: [The Power of Three, firstActivatedBy, Prue Halliwell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstActivatedBy Context triple: [The Power of Three, firstActivatedBy, Prue Halliwell]
-
A.
firstActivatedIn
Indicates the point in time or context when an entity was initially activated or became operational.
-
B.
firstUsedBy
chosen
Indicates that something was initially utilized, applied, or employed by a particular entity before any others.
-
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.
firstRaisedBy
Indicates that one entity was the earliest or original source to bring up, introduce, or initiate the referenced issue, idea, or topic in relation to another entity.
-
E.
firstEncounteredBy
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
- F. None of above.
Provenance (4 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_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2958edd500819082e07fe7830df240 |
completed | June 10, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
Created at: April 29, 2026, 8:21 p.m.