Triple
T22750388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute for Conflict Management |
E562677
|
entity |
| Predicate | servesContext |
P2919
|
FINISHED |
| Object | professional contexts |
—
|
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: professional contexts | Statement: [Institute for Conflict Management, servesContext, professional contexts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesContext Context triple: [Institute for Conflict Management, servesContext, professional contexts]
-
A.
supplyContext
Indicates that one entity provides relevant background information or situational details that clarify or frame another entity, action, or statement.
-
B.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
-
C.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs of another entity.
-
D.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
-
E.
contextOf
chosen
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b8e9408190b251700d3386a1b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.