Triple
T28721809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Novak |
E730115
|
entity |
| Predicate | powerTriggeredBy |
P14894
|
FINISHED |
| Object | strong emotions |
—
|
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: strong emotions | Statement: [Sydney Novak, powerTriggeredBy, strong emotions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerTriggeredBy Context triple: [Sydney Novak, powerTriggeredBy, strong emotions]
-
A.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
B.
powerDependsOn
chosen
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
C.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
D.
powerTarget
Indicates that one entity is the intended recipient or object of another entity’s power, influence, or energy.
-
E.
powerTarget
Indicates that an entity is the intended recipient or object of another entity’s power, influence, or energy.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 5:54 a.m.