Triple
T33096463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sequent calculus |
E846921
|
entity |
| Predicate | hasLogicalRule |
P2846
|
FINISHED |
| Object | introduction rule |
—
|
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: introduction rule | Statement: [sequent calculus, hasLogicalRule, introduction rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogicalRule Context triple: [sequent calculus, hasLogicalRule, introduction rule]
-
A.
hasLogicalFunction
Indicates that one entity serves as the logical function, role, or purpose of another within a system or structure.
-
B.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
hasLogicalStructure
Indicates that one entity possesses or exhibits a specific underlying logical organization or pattern defined by another entity.
-
D.
hasLogicalIdentifier
Indicates that an entity is associated with a specific logical identifier used to uniquely reference or distinguish it within an information or data model.
-
E.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
- 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_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 1, 2026, 1:26 a.m.