Triple
T14254660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MeSH qualifiers |
E353352
|
entity |
| Predicate | hasScopeNote |
P5018
|
FINISHED |
| Object | each qualifier has a defined scope of use |
—
|
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: each qualifier has a defined scope of use | Statement: [MeSH qualifiers, hasScopeNote, each qualifier has a defined scope of use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScopeNote Context triple: [MeSH qualifiers, hasScopeNote, each qualifier has a defined scope of use]
-
A.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
B.
hasDisambiguationNote
Indicates that there is an explanatory note used to distinguish this entity or term from other entities or terms with similar or identical names.
-
C.
notabilityScope
Indicates the domain, field, or context within which something is considered notable or significant.
-
D.
scopeOfUse
chosen
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
E.
hasBibliographicCategory
Indicates that an entity is associated with a specific bibliographic classification or category within a cataloging or documentation system.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6297f38c819090d7c7fd8bfa2e9e |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:09 a.m.