Triple
T26355088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Majesty of Love |
E663020
|
entity |
| Predicate | describesLoveAs |
P102600
|
FINISHED |
| Object | higher vibrational state |
—
|
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: higher vibrational state | Statement: [The Majesty of Love, describesLoveAs, higher vibrational state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesLoveAs Context triple: [The Majesty of Love, describesLoveAs, higher vibrational state]
-
A.
attitudeTowardLove
chosen
Indicates an entity’s feelings, beliefs, or stance regarding the concept or experience of love.
-
B.
romanticFeeling
Indicates that one entity experiences romantic attraction or affection toward another entity.
-
C.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
D.
romanticAssociation
Indicates a romantic relationship or involvement exists between the associated entities.
-
E.
romanticThemeExpressedThrough
Indicates that a romantic theme is conveyed or manifested through a particular medium, element, or aspect of a work or situation.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 10:48 p.m.