Triple
T33027588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REST |
E845082
|
entity |
| Predicate | replyCodeOnSuccess |
P33257
|
FINISHED |
| Object | 350 |
—
|
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: 350 | Statement: [REST, replyCodeOnSuccess, 350]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replyCodeOnSuccess Context triple: [REST, replyCodeOnSuccess, 350]
-
A.
returnsOnSuccess
Indicates that an operation or function completes successfully and yields a return value or proceeds to a specified outcome only when no errors occur.
-
B.
exportSuccess
Indicates that an attempted export operation completed successfully.
-
C.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
D.
denotesSuccess
Indicates that an action, process, or operation has achieved its intended goal or outcome successfully.
-
E.
returnStatus
Indicates the current outcome or condition of a previously initiated return action 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.