Triple
T31162703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For Marx |
E794383
|
entity |
| Predicate | criticalTarget |
P171202
|
FINISHED |
| Object | Hegelian Marxism |
—
|
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: Hegelian Marxism | Statement: [For Marx, criticalTarget, Hegelian Marxism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criticalTarget Context triple: [For Marx, criticalTarget, Hegelian Marxism]
-
A.
criticalTo
Indicates that one entity is essential or indispensable for the functioning, success, or existence of another entity.
-
B.
criticality
Indicates the degree of importance, urgency, or potential impact associated with an entity, condition, or situation within a given context.
-
C.
criticalDescription
Indicates that one entity provides an evaluative or analytical description of another entity, often highlighting strengths, weaknesses, or significance.
-
D.
criticalStrip
Indicates that something lies within the critical strip, the region of complex values whose real parts fall between 0 and 1.
-
E.
criticalLine
Indicates that one entity is a crucial or decisive line (such as a boundary, path, or threshold) whose state or position significantly affects the other entity or overall system.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6f01e881908fa84f5d429d37ae |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:07 p.m.