Triple
T23737919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heterotic supergravity |
E586586
|
entity |
| Predicate | cancelsAnomaliesVia |
P153492
|
FINISHED |
| Object | Green–Schwarz mechanism |
—
|
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: Green–Schwarz mechanism | Statement: [heterotic supergravity, cancelsAnomaliesVia, Green–Schwarz mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancelsAnomaliesVia Context triple: [heterotic supergravity, cancelsAnomaliesVia, Green–Schwarz mechanism]
-
A.
cancels
Indicates that one entity invalidates, nullifies, or stops the effect, operation, or scheduled occurrence of another entity or action.
-
B.
hasAnomaly
Indicates that an entity exhibits, contains, or is associated with an irregular, abnormal, or unexpected condition or feature.
-
C.
launchAnomaly
Indicates that an unexpected or abnormal condition occurred during the launch process of a system, vehicle, or mission.
-
D.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific entity.
-
E.
canceledAfter
Indicates that one event or action was canceled at a point in time occurring after another specified event or action.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad356c88190ae29ce403145ee73 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:11 p.m.