Triple
T34415957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negation |
E883403
|
entity |
| Predicate | hasTruthTableRow |
P25794
|
FINISHED |
| Object | if p is true then ¬p is false |
—
|
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: if p is true then ¬p is false | Statement: [Negation, hasTruthTableRow, if p is true then ¬p is false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTruthTableRow Context triple: [Negation, hasTruthTableRow, if p is true then ¬p is false]
-
A.
hasRow
chosen
Indicates that one entity contains, includes, or is associated with a specific row within a structured arrangement such as a table, grid, or dataset.
-
B.
hasRowState
Indicates that an entity is associated with a particular state or status of a row within a structured dataset or table.
-
C.
hasCol
Indicates that one entity possesses, contains, or is associated with a particular color.
-
D.
hasOwnTable
Indicates that an entity is associated with or requires a dedicated, separate table (e.g., in a database or data model) rather than sharing one with others.
-
E.
hasCells
Indicates that an entity contains, is composed of, or is associated with one or more cells.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 1, 2026, 1:59 a.m.