Triple
T33096455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sequent calculus |
E846921
|
entity |
| Predicate | typicalSequentForm |
P12789
|
FINISHED |
| Object | Γ ⊢ Δ |
—
|
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: Γ ⊢ Δ | Statement: [sequent calculus, typicalSequentForm, Γ ⊢ Δ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSequentForm Context triple: [sequent calculus, typicalSequentForm, Γ ⊢ Δ]
-
A.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
B.
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.
-
C.
canBeFormalizedAs
Indicates that one concept, statement, or system can be represented, expressed, or captured within a formal framework or formal language.
-
D.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
E.
isCanonicalFormOf
Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.