Triple
T3417245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medical Anthropology Quarterly |
E72037
|
entity |
| Predicate | publishesMethodology |
P49337
|
FINISHED |
| Object | qualitative research |
—
|
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: qualitative research | Statement: [Medical Anthropology Quarterly, publishesMethodology, qualitative research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesMethodology Context triple: [Medical Anthropology Quarterly, publishesMethodology, qualitative research]
-
A.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
B.
publishingModel
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
C.
hasMethodologyDocument
Indicates that an entity is associated with, or supported by, a specific methodology document that defines its procedures or approach.
-
D.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
E.
disciplinaryMethod
Indicates a method or approach used to discipline, correct, or control another party’s behavior.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92c20fc81909b5debced20ec083 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb23d23088190aeafe1379eae2eaa |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.