Triple
T33027665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKD |
E845084
|
entity |
| Predicate | effectOnServerState |
P40373
|
FINISHED |
| Object | creates new directory entry |
—
|
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: creates new directory entry | Statement: [MKD, effectOnServerState, creates new directory entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnServerState Context triple: [MKD, effectOnServerState, creates new directory entry]
-
A.
effectOnSystem
chosen
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
B.
effectOnWorld
Indicates how an entity’s actions or existence change, influence, or impact the state of the world.
-
C.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
D.
effectOnUsage
Indicates how one factor or condition changes the way something is used, including the extent, manner, or frequency of its usage.
-
E.
effectOnFlags
Indicates how an action or event changes, sets, or influences the state of one or more flags.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:23 a.m.