Triple
T21763267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-3-SAT |
E537214
|
entity |
| Predicate | searchSpace |
P145840
|
FINISHED |
| Object | all truth assignments to Boolean variables |
—
|
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: all truth assignments to Boolean variables | Statement: [Max-3-SAT, searchSpace, all truth assignments to Boolean variables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchSpace Context triple: [Max-3-SAT, searchSpace, all truth assignments to Boolean variables]
-
A.
seedSpace
Indicates a relationship where an entity provides or occupies an initial area, context, or capacity from which growth, development, or further allocation can begin.
-
B.
targetSpace
Indicates the space, area, or region toward which an action, movement, or effect is directed.
-
C.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
D.
observationSpace
Indicates the defined set of possible observations or sensory inputs that an agent can receive from its environment.
-
E.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
- 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_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. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.