Triple
T14256643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleene strong three-valued logic |
E353399
|
entity |
| Predicate | supportsPartialValuations |
P113466
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kleene strong three-valued logic, supportsPartialValuations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPartialValuations Context triple: [Kleene strong three-valued logic, supportsPartialValuations, yes]
-
A.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
B.
hasCanonicalValuation
Indicates that an entity is associated with its standard or officially recognized valuation or assessed value.
-
C.
supportsValue
Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
-
D.
partiallySupportedBy
Indicates that something receives incomplete, limited, or not fully sufficient support from another entity.
-
E.
supportsPartialMatch
Indicates that the relationship or operation allows matching based on a subset or portion of the target criteria rather than requiring a complete or exact match.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62992a188190bc046fbab5a149d6 |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:09 a.m.