Triple

T4390181
Position Surface form Disambiguated ID Type / Status
Subject hierarchy of needs E99342 entity
Predicate oftenExtendedHighestLevel P56330 FINISHED
Object self-transcendence needs 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: self-transcendence needs | Statement: [hierarchy of needs, oftenExtendedHighestLevel, self-transcendence needs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oftenExtendedHighestLevel
Context triple: [hierarchy of needs, oftenExtendedHighestLevel, self-transcendence needs]
  • A. formerHighest
    Indicates that an entity once held the highest rank, position, or status in a given context but no longer does.
  • B. highestPass
    Indicates that an entity has achieved the greatest passing value, score, or level among a set of compared entities.
  • C. highestOrgan
    Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
  • D. advancedThrough
    Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
  • E. aboveLeague
    Indicates that one entity is in a higher league, tier, or competitive level than another.
  • F. None of above. chosen

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_69b3454f739481909ff6c28331f0c0b9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35282cb2c8190856da20bb87e88ff completed March 12, 2026, 11:55 p.m.
PD Predicate disambiguation batch_69b34f572efc8190bad1e5078cbcb75a completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b3501834448190bedf775a80da4778 completed March 12, 2026, 11:45 p.m.
Created at: March 12, 2026, 11:19 p.m.