Triple
T33027650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKD |
E845084
|
entity |
| Predicate | typicalSuccessCode |
—
|
GENERATED |
| Object | 257 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSuccessCode Context triple: [MKD, typicalSuccessCode, 257]
-
A.
exportSuccess
Indicates that an attempted export operation completed successfully.
-
B.
isSuccessful
Indicates that an action, process, or attempt has achieved its intended goal or outcome.
-
C.
denotesSuccess
Indicates that an action, process, or operation has achieved its intended goal or outcome successfully.
-
D.
succeedsBy
Indicates that one entity comes after or replaces another in a sequence, order, or position.
-
E.
conditionForSuccess
Indicates that one factor must be present or satisfied in order for another factor, outcome, or process to be successful.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: May 1, 2026, 1:23 a.m.