Triple
T21763289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-3-SAT |
E537214
|
entity |
| Predicate | literalType |
P13707
|
FINISHED |
| Object | variable or its negation |
—
|
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: variable or its negation | Statement: [Max-3-SAT, literalType, variable or its negation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literalType Context triple: [Max-3-SAT, literalType, variable or its negation]
-
A.
logicalType
Indicates that one entity is classified as a logical type or category used to define or constrain the logical behavior or interpretation of another entity.
-
B.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
-
C.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
D.
symbolType
chosen
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
E.
logicType
Indicates the specific kind or category of logical system, rule, or reasoning framework that an entity or statement belongs to.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a711dc8190a786c9849dc344e8 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.