Triple
T18923942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATCvet |
E462929
|
entity |
| Predicate | usesCodeType |
P2202
|
FINISHED |
| Object | alphanumeric codes |
—
|
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: alphanumeric codes | Statement: [ATCvet, usesCodeType, alphanumeric codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCodeType Context triple: [ATCvet, usesCodeType, alphanumeric codes]
-
A.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
B.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
C.
usesCodeOfPoints
Indicates that one entity evaluates or governs something according to the rules and scoring system defined by another entity’s code of points.
-
D.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
E.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
- 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.