Triple
T22381873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward–Takahashi identities |
E553293
|
entity |
| Predicate | breaksDownIf |
P14242
|
FINISHED |
| Object | quantum anomaly is present |
—
|
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: quantum anomaly is present | Statement: [Ward–Takahashi identities, breaksDownIf, quantum anomaly is present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksDownIf Context triple: [Ward–Takahashi identities, breaksDownIf, quantum anomaly is present]
-
A.
breaksDownWhen
chosen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
B.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from another entity.
-
C.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
D.
isBrokenBy
Indicates that one entity causes another entity to become damaged, nonfunctional, or destroyed.
-
E.
includesBreakdownsBy
Indicates that something contains or presents detailed subdivisions or component analyses organized according to a specified criterion or entity.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582cce608190b5324b30f349a3ff |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.