Triple
T27818469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetRequest |
E702746
|
entity |
| Predicate | hasErrorCondition |
P144597
|
FINISHED |
| Object | resource not found |
—
|
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: resource not found | Statement: [GetRequest, hasErrorCondition, resource not found]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasErrorCondition Context triple: [GetRequest, hasErrorCondition, resource not found]
-
A.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
hasErrorType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of error.
-
C.
hasConditionCodes
Indicates that an entity is associated with one or more standardized condition codes describing its state, status, or circumstances.
-
D.
hasNumberOfConditions
Indicates that an entity is associated with a specific count of conditions it has or is subject to.
-
E.
hasErrorLogging
Indicates that an entity is equipped with or supports functionality for recording and tracking errors or failures.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 5:47 p.m.