Triple
T1668710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQLite |
E36073
|
entity |
| Predicate | isZeroConfiguration |
P29729
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SQLite, isZeroConfiguration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isZeroConfiguration Context triple: [SQLite, isZeroConfiguration, true]
-
A.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
B.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
C.
isNonzeroFor
Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
-
D.
hasIndependentDigitZero
Indicates that an entity possesses at least one digit or numeral component that is a zero considered as a distinct, standalone element.
-
E.
isNotIndicatedFor
Indicates that a treatment, action, or option is not recommended or appropriate for a particular condition, situation, or entity.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9178d84008190a96c1429420fb374 |
completed | March 5, 2026, 5:41 a.m. |
Created at: March 4, 2026, 7:29 p.m.