Triple
T37657068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server error numbers |
E937628
|
entity |
| Predicate | reservedRange |
P189167
|
FINISHED |
| Object | 0-999 |
—
|
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: 0-999 | Statement: [SQL Server error numbers, reservedRange, 0-999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservedRange Context triple: [SQL Server error numbers, reservedRange, 0-999]
-
A.
associatedRange
Indicates that one entity is linked to or falls within a particular range defined or referenced by another entity.
-
B.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
-
C.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
E.
designedRange
Indicates the intended or specified range within which something is designed to operate or be effective.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbb9e69b7481909beaf8264d87c5e5 |
completed | May 6, 2026, 10 p.m. |
Created at: May 3, 2026, 4:18 p.m.