Triple
T18923655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Health Professions Alliance |
E462923
|
entity |
| Predicate | representsProfession |
P69514
|
FINISHED |
| Object | physicians |
—
|
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: physicians | Statement: [World Health Professions Alliance, representsProfession, physicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsProfession Context triple: [World Health Professions Alliance, representsProfession, physicians]
-
A.
representsProfessionIn
Indicates that an entity holds or is associated with a particular profession within a specified context, domain, or location.
-
B.
portraysProfession
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
-
C.
memberProfession
Indicates that a member or individual holds or practices a particular profession or occupation.
-
D.
recognizesProfession
Indicates that one entity acknowledges or identifies another entity’s professional role or occupation as such.
-
E.
includesProfession
chosen
Indicates that one entity’s set of attributes, roles, or members contains a specific profession as part of it.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b549448190850d7eed4de7872b |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.