Triple
T21763299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-3-SAT |
E537214
|
entity |
| Predicate | formulaStructure |
P79480
|
FINISHED |
| Object | conjunction of 3-literal clauses |
—
|
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: conjunction of 3-literal clauses | Statement: [Max-3-SAT, formulaStructure, conjunction of 3-literal clauses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formulaStructure Context triple: [Max-3-SAT, formulaStructure, conjunction of 3-literal clauses]
-
A.
formulaType
chosen
Indicates the specific kind or category of formula associated with an entity or expression.
-
B.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
C.
structureFunction
Indicates that one entity’s physical or organizational structure serves a particular function or role in relation to another entity.
-
D.
primaryFormulaFormat
Indicates the main or default structural format in which a formula is represented or stored.
-
E.
finStructure
Indicates a relationship where one entity specifies or characterizes the fin-related structural features or configuration of another entity.
- 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.