Triple
T6050301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .md |
E134773
|
entity |
| Predicate | popularBecauseOfAbbreviation |
P36183
|
FINISHED |
| Object | MD meaning Doctor of Medicine |
—
|
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: MD meaning Doctor of Medicine | Statement: [.md, popularBecauseOfAbbreviation, MD meaning Doctor of Medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularBecauseOfAbbreviation Context triple: [.md, popularBecauseOfAbbreviation, MD meaning Doctor of Medicine]
-
A.
popularName
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
B.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
C.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
D.
abbreviationUsedFor
chosen
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
E.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056f66cb08190a782cdd038f26b93 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.