Triple
T25760921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babbitt_concept_of_the_higher_will |
E648736
|
entity |
| Predicate | stressedIn |
P159240
|
FINISHED |
| Object | Democracy_and_Leadership_(book) |
—
|
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: Democracy_and_Leadership_(book) | Statement: [Babbitt_concept_of_the_higher_will, stressedIn, Democracy_and_Leadership_(book)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stressedIn Context triple: [Babbitt_concept_of_the_higher_will, stressedIn, Democracy_and_Leadership_(book)]
-
A.
stressed
Indicates that an entity is experiencing psychological or emotional strain or pressure, often due to challenging or demanding circumstances.
-
B.
hasStress
Indicates that an entity is experiencing or exhibiting psychological or physiological stress.
-
C.
representsStressOf
Indicates that one entity expresses, reflects, or denotes the stress experienced by another entity.
-
D.
stressType
Indicates the specific kind or category of stress associated with or affecting an entity.
-
E.
stricken
Indicates that an entity has been severely affected, harmed, or afflicted by something (such as illness, disaster, or misfortune).
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdeef1348190a32e4ae429680b7d |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 5:05 a.m.