Triple
T23953782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamabe problem |
E603721
|
entity |
| Predicate | gapCorrectedBy |
P14270
|
FINISHED |
| Object | Neil Trudinger |
—
|
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: Neil Trudinger | Statement: [Yamabe problem, gapCorrectedBy, Neil Trudinger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gapCorrectedBy Context triple: [Yamabe problem, gapCorrectedBy, Neil Trudinger]
-
A.
canBeCorrectedBy
Indicates that something has the potential to be made accurate, fixed, or improved through the intervention or action of a specified agent or method.
-
B.
gapBetween
Indicates the spatial or temporal distance or separation that exists between two entities.
-
C.
fixedBy
chosen
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
D.
includesCorrectionsFor
Indicates that one item contains modifications, fixes, or amendments that address errors or issues present in another item.
-
E.
correctionType
Indicates the specific kind or category of correction that has been applied to or 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.