Triple
T18479111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fundamental theorem of arithmetic |
E451510
|
entity |
| Predicate | doesNotHoldIn |
P89288
|
FINISHED |
| Object | all integral domains |
—
|
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: all integral domains | Statement: [fundamental theorem of arithmetic, doesNotHoldIn, all integral domains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotHoldIn Context triple: [fundamental theorem of arithmetic, doesNotHoldIn, all integral domains]
-
A.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
B.
notHeldIn
chosen
Indicates that an event, activity, or state does not take place or is not located within a specified context, location, or time frame.
-
C.
notHeldDuring
Indicates that a specified condition, event, or relationship does not occur or is not in effect throughout a given time interval or temporal context.
-
D.
notAutomaticallyHeldBy
Indicates that a particular right, status, or condition is not granted or possessed by default and must be explicitly obtained or established.
-
E.
doesNotHave
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53065e8388190bb216dae89f8cf75 |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.