Triple
T8645566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Cloud |
E204764
|
entity |
| Predicate | focusIndustry |
P24922
|
FINISHED |
| Object | healthcare |
—
|
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: healthcare | Statement: [Microsoft Cloud, focusIndustry, healthcare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusIndustry Context triple: [Microsoft Cloud, focusIndustry, healthcare]
-
A.
industrialFocus
Indicates a relationship where an entity is primarily concerned with, specialized in, or directed toward a particular industrial sector or area of industrial activity.
-
B.
industryContext
chosen
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
employerFocus
Indicates that an employer directs particular attention, resources, or priority toward a specific subject, group, or area.
-
E.
industryStart
Indicates the point in time or event at which an industry, industrial activity, or industrial era begins.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc479999c881908c0c4e01c07d02d4 |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.