Triple
T32964964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hegelians |
E843343
|
entity |
| Predicate | interpretedWorkOf |
P118293
|
FINISHED |
| Object | Georg Wilhelm Friedrich Hegel |
—
|
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: Georg Wilhelm Friedrich Hegel | Statement: [Old Hegelians, interpretedWorkOf, Georg Wilhelm Friedrich Hegel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretedWorkOf Context triple: [Old Hegelians, interpretedWorkOf, Georg Wilhelm Friedrich Hegel]
-
A.
interpretedWork
chosen
Indicates that one entity is a performance, rendition, or interpretation of another underlying work (such as a composition, script, or original piece).
-
B.
translatedWorkOf
Indicates that one work is a translation of another original work.
-
C.
coverOfWorkBy
Indicates that one work is a cover version or performance of another work originally created by a specified creator or artist.
-
D.
compilesWorkOf
Indicates that one entity gathers, edits, or assembles the works created by another entity into a collection or compilation.
-
E.
backedWorkOf
Indicates that one entity has provided support, endorsement, or resources to enable or promote the work produced by another entity.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 1:21 a.m.