Triple
T22020675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega Mimic |
E543835
|
entity |
| Predicate | encounterFrequency |
P146293
|
FINISHED |
| Object | very rare |
—
|
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: very rare | Statement: [Omega Mimic, encounterFrequency, very rare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterFrequency Context triple: [Omega Mimic, encounterFrequency, very rare]
-
A.
complicationFrequency
Indicates how often complications occur in relation to a given procedure, condition, or intervention.
-
B.
encountered
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
C.
inspectionFrequency
Indicates how often an entity is examined, checked, or reviewed within a given time period.
-
D.
encounterLocation
Indicates the place or setting where two or more entities meet, interact, or come into contact.
-
E.
occurrence
Indicates that an event, state, or condition takes place or happens at a particular time or in a particular context.
- F. None of above. chosen
Provenance (4 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c7b3308190ac056bef6f82722e |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:23 p.m.