Triple
T7101186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Radiology |
E165461
|
entity |
| Predicate | mayIncludeUnit |
P53912
|
FINISHED |
| Object | interventional radiology unit |
—
|
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: interventional radiology unit | Statement: [Department of Radiology, mayIncludeUnit, interventional radiology unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeUnit Context triple: [Department of Radiology, mayIncludeUnit, interventional radiology unit]
-
A.
basedUnitsInclude
Indicates that a composite or derived unit is defined using, and therefore includes, the specified base unit(s) in its construction.
-
B.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
C.
mayIncludeFeature
chosen
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
D.
multipleUnit
Indicates that an entity is composed of or associated with more than one unit of the same type.
-
E.
minorUnitUsage
Indicates how a minor or subordinate unit is used or functions in relation to a larger or primary unit.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e586b7208190bab9429ded35ba4f |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.