Triple
T28001694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Being (Sein) |
E707163
|
entity |
| Predicate | forgottenIn |
P163613
|
FINISHED |
| Object | history of metaphysics |
—
|
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: history of metaphysics | Statement: [Being (Sein), forgottenIn, history of metaphysics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forgottenIn Context triple: [Being (Sein), forgottenIn, history of metaphysics]
-
A.
forgets
Indicates that an entity fails to remember or loses awareness of something that was previously known or intended.
-
B.
rememberedThrough
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
C.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
D.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or context.
-
E.
erasesMemoriesOf
Indicates that one entity causes the memories of another entity to be removed or wiped out.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd17884819090b08f0819bebe78 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:57 p.m.