Triple
T23009429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contingent (Eva Hesse) |
E572865
|
entity |
| Predicate | conditionIssue |
P133168
|
FINISHED |
| Object | latex deterioration |
—
|
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: latex deterioration | Statement: [Contingent (Eva Hesse), conditionIssue, latex deterioration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionIssue Context triple: [Contingent (Eva Hesse), conditionIssue, latex deterioration]
-
A.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
B.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
C.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
D.
statusIssue
chosen
Indicates that an entity has a problem, defect, or irregular condition affecting its normal or expected status.
-
E.
possibleIssue
Indicates that there is a potential or suspected problem, defect, or undesired condition associated with the referenced entity or situation, though it is not yet confirmed.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835919b08190ba78e182b87358d4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.