Triple
T8521937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IHE Laboratory |
E201712
|
entity |
| Predicate | definesProfileFor |
P13755
|
FINISHED |
| Object | laboratory order management |
—
|
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: laboratory order management | Statement: [IHE Laboratory, definesProfileFor, laboratory order management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProfileFor Context triple: [IHE Laboratory, definesProfileFor, laboratory order management]
-
A.
definesProfileType
chosen
Indicates that an entity specifies or assigns the particular profile type associated with another entity.
-
B.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
C.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
-
D.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
E.
stagingProfile
Indicates a temporary or preparatory configuration or environment used before final deployment or release.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe62a490481908ee0ad4ba9a94682 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.