Triple
T28003209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aufhebung |
E707200
|
entity |
| Predicate | centralInWork |
P4751
|
FINISHED |
| Object | Phenomenology of Spirit |
—
|
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: Phenomenology of Spirit | Statement: [Aufhebung, centralInWork, Phenomenology of Spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralInWork Context triple: [Aufhebung, centralInWork, Phenomenology of Spirit]
-
A.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
B.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centralProject
Indicates that one project serves as the primary or core project around which other related projects or activities are organized.
-
D.
centralRequest
Indicates that an entity serves as the primary or main request within a broader set of related requests or interactions.
-
E.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 7:58 p.m.