Triple

T33541340
Position Surface form Disambiguated ID Type / Status
Subject SpiritualBliss E859077 entity
Predicate experiencedAs P141157 FINISHED
Object inner stillness 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: inner stillness | Statement: [SpiritualBliss, experiencedAs, inner stillness]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: experiencedAs
Context triple: [SpiritualBliss, experiencedAs, inner stillness]
  • A. hasExperienceOf chosen
    Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
  • B. usedExperienceIn
    Indicates that an entity applied or leveraged a particular experience or expertise in performing an action or achieving a result.
  • C. allegedlyExperienced
    Indicates that an entity is claimed or reported to have undergone or had a particular experience, without asserting that the experience actually occurred.
  • D. experienceIncludes
    Indicates that a particular experience encompasses, contains, or involves a specified component, activity, or element as part of it.
  • E. hasPastExperience
    Indicates that an entity has previously engaged in or undergone the specified activity, role, or situation in the past.
  • 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_69f3497a5be08190a39b12736899e034 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fb19063c81909466b329655c8583 completed May 3, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69f6f96badb08190994442c2aba840b1 completed May 3, 2026, 7:29 a.m.
Created at: May 1, 2026, 1:39 a.m.