Triple
T10356885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Medical Association headquarters |
E244017
|
entity |
| Predicate | servesGroup |
P93846
|
FINISHED |
| Object | medical doctors |
—
|
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 doctors | Statement: [British Medical Association headquarters, servesGroup, medical doctors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesGroup Context triple: [British Medical Association headquarters, servesGroup, medical doctors]
-
A.
servedNativeGroup
Indicates that one entity provided service, assistance, or work to a particular native or indigenous group.
-
B.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
C.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
D.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
E.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
- F. None of above. chosen
Provenance (4 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e954a0b8819083e4bd1fa47dc6f5 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:58 a.m.