Triple
T20885078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | linear logic |
E514255
|
entity |
| Predicate | hasProofSystem |
P7024
|
FINISHED |
| Object | sequent calculus |
—
|
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: sequent calculus | Statement: [linear logic, hasProofSystem, sequent calculus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProofSystem Context triple: [linear logic, hasProofSystem, sequent calculus]
-
A.
hasProofMethod
chosen
Indicates that there exists a specific method or technique used to establish or demonstrate the validity of something (such as a statement, claim, or theorem).
-
B.
hasElementaryProof
Indicates that there exists a proof of the statement using only elementary methods, without relying on advanced or sophisticated theories.
-
C.
usesProofLanguage
Indicates that one entity employs a specific formal or structured language to express or present a proof related to another entity.
-
D.
partialProofBy
Indicates that one entity serves as an incomplete or intermediate proof contributing toward the full proof of another entity.
-
E.
laterProofBy
Indicates that one proof is derived or established after, and possibly building upon, an earlier proof.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67c9d1c81908031eb77c124f119 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.