Triple
T875623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNOMED CT |
E18910
|
entity |
| Predicate | hasReleaseCycle |
P16199
|
FINISHED |
| Object | regular scheduled releases |
—
|
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: regular scheduled releases | Statement: [SNOMED CT, hasReleaseCycle, regular scheduled releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseCycle Context triple: [SNOMED CT, hasReleaseCycle, regular scheduled releases]
-
A.
standardReleaseCadence
chosen
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
B.
hasLiturgicalCycle
Indicates that one entity follows, observes, or is structured according to a particular liturgical cycle associated with another entity.
-
C.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
-
D.
hasDeployment
Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
-
E.
hasSpecialVersion
Indicates that an entity possesses or is associated with a distinct or customized version of another entity, differing from the standard or default form.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acae12948190923d31966c26a130 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.