Triple
T33487175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Minsk Group |
E857642
|
entity |
| Predicate | hasProcessName |
—
|
GENERATED |
| Object | Minsk process |
—
|
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: hasProcessName Context triple: [OSCE Minsk Group, hasProcessName, Minsk process]
-
A.
hasServiceName
Indicates that an entity is associated with or identified by a specific service name.
-
B.
hasComponentName
Indicates that an entity includes or is associated with a component identified by a specific name.
-
C.
hasPortName
Indicates that one entity is identified by or associated with a specific port name.
-
D.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
E.
hasNameString
chosen
Indicates that an entity is associated with a specific textual string used as its name.
- F. None of above.
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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.