Triple
T33027651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKD |
E845084
|
entity |
| Predicate | successResponseExample |
P97013
|
FINISHED |
| Object | 257 "dirname" created |
—
|
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: 257 "dirname" created | Statement: [MKD, successResponseExample, 257 "dirname" created]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successResponseExample Context triple: [MKD, successResponseExample, 257 "dirname" created]
-
A.
responseExample
chosen
Indicates that one entity serves as an illustrative or sample response corresponding to another entity (such as a prompt, question, or situation).
-
B.
exportSuccess
Indicates that an attempted export operation completed successfully.
-
C.
successRecord
Indicates that an entity has a recorded instance of achieving a successful outcome in a particular context or activity.
-
D.
typicalResponse
Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
-
E.
failureResponseCodeExample
Indicates the example HTTP status code that should be returned when the related operation fails.
- 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_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:23 a.m.