Triple
T1308814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHO regional office network |
E27941
|
entity |
| Predicate | supportsEntity |
P16415
|
FINISHED |
| Object | WHO member states |
—
|
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: WHO member states | Statement: [WHO regional office network, supportsEntity, WHO member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEntity Context triple: [WHO regional office network, supportsEntity, WHO member states]
-
A.
providesSupportTo
chosen
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
B.
supportsOrganization
Indicates that one entity provides assistance, resources, or advocacy that helps sustain or advance an organization.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
-
E.
supportsDocument
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.