Triple
T17230065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilbert-style deductive systems |
E418216
|
entity |
| Predicate | typicalAxiomForm |
P12789
|
FINISHED |
| Object | implication axioms |
—
|
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: implication axioms | Statement: [Hilbert-style deductive systems, typicalAxiomForm, implication axioms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAxiomForm Context triple: [Hilbert-style deductive systems, typicalAxiomForm, implication axioms]
-
A.
axiom2
Indicates that the relationship or action is taken as a fundamental, assumed truth within the system, serving as a base rule from which other statements are derived.
-
B.
foundationAxiomHoldsIn
Indicates that the foundation (or regularity) axiom is satisfied within a given model, structure, or context.
-
C.
requiresAxiom
Indicates that one element depends on a specific axiom as a necessary basis or justification for its validity or use.
-
D.
hasAxiom
Indicates that an entity is associated with, defined by, or governed through a specific axiom or set of axioms.
-
E.
typicalForm
chosen
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42df62ec48190b2ed633a5bcc0255 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.