Triple
T26992502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3-SAT |
E679892
|
entity |
| Predicate | satisfiabilityType |
P162022
|
FINISHED |
| Object | exactly three literals per clause |
—
|
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: exactly three literals per clause | Statement: [3-SAT, satisfiabilityType, exactly three literals per clause]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satisfiabilityType Context triple: [3-SAT, satisfiabilityType, exactly three literals per clause]
-
A.
satisfies
Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
-
B.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
C.
logicType
Indicates the specific kind or category of logical system, rule, or reasoning framework that an entity or statement belongs to.
-
D.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
reasoningType
Indicates the specific kind or mode of reasoning applied in deriving a conclusion or making an inference between entities.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 6:52 a.m.