Triple
T26992470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAT |
E679891
|
entity |
| Predicate | literalDefinition |
P3918
|
FINISHED |
| Object | variable or its negation |
—
|
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: variable or its negation | Statement: [SAT, literalDefinition, variable or its negation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literalDefinition Context triple: [SAT, literalDefinition, variable or its negation]
-
A.
symbolicDefinition
Indicates that one entity serves as a formal symbolic representation or definition of another entity within a given system or context.
-
B.
definitionText
Indicates the textual content that provides the definition or explanatory meaning of a concept, term, or entity.
-
C.
hasLiteralMeaning
chosen
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
D.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
E.
clauseDefinition
Indicates that one entity specifies or provides the formal definition or content of a particular clause associated with 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 6:52 a.m.