Triple
T31646315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCF |
E807592
|
entity |
| Predicate | coreLogic |
P172059
|
FINISHED |
| Object | intuitionistic higher-order logic |
—
|
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: intuitionistic higher-order logic | Statement: [LCF, coreLogic, intuitionistic higher-order logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreLogic Context triple: [LCF, coreLogic, intuitionistic higher-order logic]
-
A.
claimsAboutLogic
Indicates that one entity makes statements or assertions concerning the principles, rules, or properties of logic in relation to another entity or topic.
-
B.
coreFusion
Indicates a relationship where two or more central or fundamental components are merged into a single unified core.
-
C.
core
Indicates a central, most important, or foundational part of something in relation to its surrounding or supporting elements.
-
D.
coreConstruct
Indicates a fundamental building or organizing relationship where one entity serves as the essential basis or primary component from which another entity is formed or structured.
-
E.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
- F. None of above. chosen
Provenance (4 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:51 p.m.