Triple
T446705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHO Regional Office for Europe |
E7035
|
entity |
| Predicate | hasParentRegion |
P285
|
FINISHED |
| Object | global WHO Secretariat |
—
|
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: global WHO Secretariat | Statement: [WHO Regional Office for Europe, hasParentRegion, global WHO Secretariat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentRegion Context triple: [WHO Regional Office for Europe, hasParentRegion, global WHO Secretariat]
-
A.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
hasNoParentZone
Indicates that an entity exists independently and is not contained within or subordinate to any parent zone.
-
C.
hasParentCategory
Indicates that an entity belongs to or is organized under a broader, more general category.
-
D.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
E.
hasParentSeries
Indicates that a work or item belongs to, or is derived from, a broader parent series.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef62c7a88190851fcd57658b4102 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.