Triple
T8418750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Unique Identifier |
E198794
|
entity |
| Predicate | forbidsCharacter |
P272
|
FINISHED |
| Object | leading zero in a component |
—
|
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: leading zero in a component | Statement: [DICOM Unique Identifier, forbidsCharacter, leading zero in a component]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forbidsCharacter Context triple: [DICOM Unique Identifier, forbidsCharacter, leading zero in a component]
-
A.
legalCharacter
Indicates that an entity possesses a status, role, or nature that is recognized and defined by law.
-
B.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
C.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
-
D.
prohibits
chosen
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
E.
doesNotAllow
Indicates that one entity prevents, forbids, or does not permit another entity from performing a specific action or being in a certain state.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c7d6e48190a2bbde89c5d42af6 |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.