Triple
T21763288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-3-SAT |
E537214
|
entity |
| Predicate | clauseType |
P58758
|
FINISHED |
| Object | disjunction of three literals |
—
|
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: disjunction of three literals | Statement: [Max-3-SAT, clauseType, disjunction of three literals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clauseType Context triple: [Max-3-SAT, clauseType, disjunction of three literals]
-
A.
constitutionalClauseType
Indicates the specific type or category of a clause within a constitution that characterizes the nature of the constitutional provision.
-
B.
allegedClause
Indicates that a clause or statement is claimed or asserted to be true, typically without confirmed proof or legal determination.
-
C.
clauseNumber
Indicates the specific numbered position or identifier assigned to a clause within a larger document or agreement.
-
D.
typeOfClause
chosen
Indicates the specific kind or category of clause that a given clause instance belongs to.
-
E.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
- 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.