Triple
T27818442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetRequest |
E702746
|
entity |
| Predicate | shouldNot |
P163383
|
FINISHED |
| Object | modify server state |
—
|
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: modify server state | Statement: [GetRequest, shouldNot, modify server state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shouldNot Context triple: [GetRequest, shouldNot, modify server state]
-
A.
notToBe
Indicates that one entity is explicitly specified as not being identical to, equivalent to, or in the state of another entity or condition.
-
B.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
D.
shouldNotBeUsedIn
Indicates that one entity is not appropriate, allowed, or recommended for use within the context, scope, or situation defined by another entity.
-
E.
shouldNotBeUsedWith
Indicates that one entity is not recommended or is prohibited from being used in combination with another 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6386cb0a08190aa7300c319d83884 |
completed | May 2, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:47 p.m.