Triple
T17060266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Marcus Welby |
E413936
|
entity |
| Predicate | settingOfPractice |
P125694
|
FINISHED |
| Object | suburban medical office |
—
|
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: suburban medical office | Statement: [Dr. Marcus Welby, settingOfPractice, suburban medical office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfPractice Context triple: [Dr. Marcus Welby, settingOfPractice, suburban medical office]
-
A.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
B.
describedPractice
Indicates that one entity has provided a description or explanation of a particular practice associated with another entity.
-
C.
approvedPractice
Indicates that a particular practice, method, or procedure has been formally reviewed and granted official approval for use or adoption.
-
D.
rulesOfPractice
Indicates the formal procedures, standards, or guidelines that govern how a particular activity, profession, or process must be conducted.
-
E.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7d2dc48190816388570fa31c2e |
completed | April 18, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.