Triple
T1048766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOM II |
E22644
|
entity |
| Predicate | occursInContextOf |
P2919
|
FINISHED |
| Object | ministerial processes |
—
|
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: ministerial processes | Statement: [SOM II, occursInContextOf, ministerial processes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInContextOf Context triple: [SOM II, occursInContextOf, ministerial processes]
-
A.
contextOf
chosen
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
B.
occurredIn
Indicates that an event or action took place within a specific location, context, or time frame.
-
C.
proposedInContextOf
Indicates that something (such as an idea, action, or change) was proposed specifically within, and in relation to, a particular situation, setting, or surrounding circumstances.
-
D.
emergedInContext
Indicates that something came into existence, became apparent, or developed within a specific situation, environment, or set of circumstances.
-
E.
occursWhen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.