Triple
T3389588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEDLINE |
E71384
|
entity |
| Predicate | indexingStandard |
P19875
|
FINISHED |
| Object | MeSH descriptors |
—
|
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: MeSH descriptors | Statement: [MEDLINE, indexingStandard, MeSH descriptors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexingStandard Context triple: [MEDLINE, indexingStandard, MeSH descriptors]
-
A.
indexingService
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
-
B.
indexStructure
Indicates that one entity serves as an index or organizational framework that structures, arranges, or provides access to another entity or set of entities.
-
C.
indexType
chosen
Indicates the classification or category of an index associated with an entity or structure.
-
D.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
E.
coreStandard
Indicates that something conforms to, is defined by, or is governed by a central or foundational standard or specification.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb666e514819090560d43bfaf55b8 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.