Triple
T1253826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fellow of the AAPM |
E26937
|
entity |
| Predicate | professionalCommunity |
P6194
|
FINISHED |
| Object | medical physicists |
—
|
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: medical physicists | Statement: [Fellow of the AAPM, professionalCommunity, medical physicists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionalCommunity Context triple: [Fellow of the AAPM, professionalCommunity, medical physicists]
-
A.
professional
Indicates that one entity has a formal, occupation-related role, service, or expertise in relation to another entity.
-
B.
businessCareer
Indicates a relationship where an entity’s professional life, roles, or progression is specifically within the field of business or commerce.
-
C.
sharesProfessionWith
Indicates that two entities have the same profession or occupational role.
-
D.
community
chosen
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
E.
careerField
Indicates the professional domain or occupational area in which an entity works or specializes.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa407a0819099399799a416152e |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.