Triple
T18923865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatomical Therapeutic Chemical Classification System |
E462927
|
entity |
| Predicate | exampleCodeRepresents |
P67580
|
FINISHED |
| Object | metformin |
—
|
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: metformin | Statement: [Anatomical Therapeutic Chemical Classification System, exampleCodeRepresents, metformin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleCodeRepresents Context triple: [Anatomical Therapeutic Chemical Classification System, exampleCodeRepresents, metformin]
-
A.
representsCode
chosen
Indicates that one entity serves as a code, encoding, or symbolic representation for another entity.
-
B.
codeExample
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
C.
codeListing
Indicates a relationship where one entity is a segment of source code that is presented or referenced as a discrete, viewable listing associated with another entity.
-
D.
scriptRepresentation
Indicates the specific written or encoded form in which something (such as language, data, or content) is expressed or represented.
-
E.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b549448190850d7eed4de7872b |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.