Triple
T28324857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | orgone energy |
E717378
|
entity |
| Predicate | basedOnEarlierIdeas |
P169246
|
FINISHED |
| Object | Freudian libido |
—
|
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: Freudian libido | Statement: [orgone energy, basedOnEarlierIdeas, Freudian libido]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEarlierIdeas Context triple: [orgone energy, basedOnEarlierIdeas, Freudian libido]
-
A.
basedOnCreativeVisionOf
Indicates that something is created, designed, or developed according to the artistic or conceptual vision conceived by a particular entity.
-
B.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
C.
basedOnInventionOf
Indicates that something is derived from, developed using, or fundamentally relies on a particular invention.
-
D.
hasBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using another entity as its source or foundation.
-
E.
basedOnEarlierCollaboration
Indicates that the relationship or action arises from, or is grounded in, a prior collaboration between the involved entities.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 28, 2026, 12:27 a.m.