Triple
T28324881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | orgone energy |
E717378
|
entity |
| Predicate | hasLaterProponent |
P191000
|
FINISHED |
| Object | Elsworth F. Baker |
—
|
NE NERFINISHED |
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: Elsworth F. Baker | Statement: [orgone energy, hasLaterProponent, Elsworth F. Baker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterProponent Context triple: [orgone energy, hasLaterProponent, Elsworth F. Baker]
-
A.
hasMainProponent
Indicates that one entity is the primary advocate, champion, or leading supporter of another entity.
-
B.
hasLaterMember
Indicates that one member in an ordered sequence occurs later than another member in that same sequence.
-
C.
hasHistoricalProponent
Indicates that an entity has been advocated, supported, or promoted by a specific person or group in the past.
-
D.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
E.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: April 28, 2026, 12:27 a.m.