Triple
T32378073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SqlCommand |
E827340
|
entity |
| Predicate | defaultCommandTimeoutSeconds |
P147913
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [SqlCommand, defaultCommandTimeoutSeconds, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultCommandTimeoutSeconds Context triple: [SqlCommand, defaultCommandTimeoutSeconds, 30]
-
A.
defaultLoginTimeout
Indicates the standard amount of time a login session or login attempt is allowed to remain active before it automatically expires or times out.
-
B.
timeoutDuration
chosen
Indicates the length of time that may elapse before an operation, request, or session is automatically terminated or considered failed.
-
C.
defaultHoldtimeSeconds
Indicates the default number of seconds an entity (such as a call, request, or process) is held or delayed before further action is taken.
-
D.
strategicTimeoutFor
Indicates that one entity initiates or designates a strategic timeout specifically for another entity (such as a team, player, or process).
-
E.
timeoutAllocation
Indicates the assignment or distribution of a specific time limit or timeout duration to an operation, resource, or process.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 12:51 a.m.