Triple
T8317068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangsaman |
E194730
|
entity |
| Predicate | hasCriticalReappraisal |
P41191
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Hangsaman, hasCriticalReappraisal, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriticalReappraisal Context triple: [Hangsaman, hasCriticalReappraisal, late 20th century]
-
A.
reassessment
chosen
Indicates that a previously made judgment, evaluation, or decision about something is being reviewed and potentially revised.
-
B.
reassessedAfter
Indicates that one entity is evaluated or reviewed again at a time point that occurs after another specified event or assessment.
-
C.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
D.
hasCriticalConcept
Indicates that one entity includes, depends on, or is defined by a key concept that is essential to understanding or functioning of another entity.
-
E.
usedToCritique
Indicates that something is employed as a means to analyze, evaluate, or express disapproval of something else.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f557a7881908adcf353f7297848 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.