Triple
T9928284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft To Do |
E192577
|
entity |
| Predicate | cloudBased |
P91172
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Microsoft To Do, cloudBased, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloudBased Context triple: [Microsoft To Do, cloudBased, true]
-
A.
cloudServiceName
Indicates the specific name assigned to a cloud-based service associated with an entity.
-
B.
typeOfCloud
Indicates the specific category or classification of a cloud within a cloud-type taxonomy or system.
-
C.
hasCloudComposition
Indicates that an atmospheric body or region possesses a specific composition or makeup of clouds.
-
D.
hasHICloud
Indicates that an entity possesses or is associated with high-intensity (HI) cloud coverage or cloud-related conditions.
-
E.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb59d7ad08190982a1584547190bd |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:43 p.m.