Triple
T10063345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasse norm theorem |
E213039
|
entity |
| Predicate | failsInGeneralFor |
P91900
|
FINISHED |
| Object | non-cyclic extensions |
—
|
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: non-cyclic extensions | Statement: [Hasse norm theorem, failsInGeneralFor, non-cyclic extensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failsInGeneralFor Context triple: [Hasse norm theorem, failsInGeneralFor, non-cyclic extensions]
-
A.
failsToConformTo
Indicates that one entity does not meet, match, or comply with the standards, rules, or expectations defined by another entity or specification.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
D.
typeOfFailure
Indicates the specific kind or category of failure that occurred in relation to an entity or process.
-
E.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd4e4ac8190a37061b4082caa48 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:58 p.m.