Triple
T34266117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seidel aberrations |
E879170
|
entity |
| Predicate | goalOfCorrection |
P64674
|
FINISHED |
| Object | improve image quality |
—
|
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: improve image quality | Statement: [Seidel aberrations, goalOfCorrection, improve image quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfCorrection Context triple: [Seidel aberrations, goalOfCorrection, improve image quality]
-
A.
goalOfCritique
Indicates that a critique is directed toward achieving or serving a particular goal or purpose.
-
B.
errorReductionGoal
Indicates that an entity has a target or objective to decrease the number or rate of errors relative to a current or baseline level.
-
C.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
goalOfRealization
Indicates the intended outcome or objective that an action, process, or plan is meant to bring into reality or achieve.
-
E.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.