Triple
T32258175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTL |
E824076
|
entity |
| Predicate | hasDecisionProblem |
P132452
|
FINISHED |
| Object | satisfiability |
—
|
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: satisfiability | Statement: [LTL, hasDecisionProblem, satisfiability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecisionProblem Context triple: [LTL, hasDecisionProblem, satisfiability]
-
A.
hasDecisionProcedure
Indicates that there exists a systematic, effective method for determining, for any given input, whether the predicate or problem in question holds or has a solution.
-
B.
hasDecisionPoint
Indicates that there is a specific moment or juncture at which a choice between alternative options or paths must be made.
-
C.
decisionProblem
chosen
Indicates that the subject is a computational problem for which the task is to decide, with a yes/no answer, whether given inputs satisfy a specified condition.
-
D.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
E.
hasDecisionMaker
Indicates that one entity serves as the decision-making authority or agent for 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 12:41 a.m.