Triple
T4390180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hierarchy of needs |
E99342
|
entity |
| Predicate | highestLevel |
P22158
|
FINISHED |
| Object | self-actualization 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-actualization needs | Statement: [hierarchy of needs, highestLevel, self-actualization needs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestLevel Context triple: [hierarchy of needs, highestLevel, self-actualization needs]
-
A.
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.
-
B.
highestPass
Indicates that an entity has achieved the greatest passing value, score, or level among a set of compared entities.
-
C.
highestCategory
Indicates that the related entity is the topmost or most specific category to which another entity is ultimately classified or assigned.
-
D.
highestPart
Indicates that one entity is the topmost or uppermost portion of another entity.
-
E.
highestWorld
chosen
Indicates that the subject entity occupies or is associated with the topmost or most elevated world, level, or realm within a defined hierarchy of worlds.
- 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_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. |
Created at: March 12, 2026, 11:19 p.m.