Triple
T35270450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClearStory Data |
E1018650
|
entity |
| Predicate | dataSourceSupport |
P46377
|
FINISHED |
| Object | cloud data sources |
—
|
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: cloud data sources | Statement: [ClearStory Data, dataSourceSupport, cloud data sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSourceSupport Context triple: [ClearStory Data, dataSourceSupport, cloud data sources]
-
A.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
B.
dataSourceFor
chosen
Indicates that one entity serves as the origin or provider of data that is used or consumed by another entity.
-
C.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
D.
dataModelSupport
Indicates that one entity provides compatibility with, or is capable of operating using, the data model defined or required by another entity.
-
E.
collectorSupports
Indicates that a collector provides backing, assistance, or endorsement to another entity or activity.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f9fabdc8190818a4032238abf08 |
completed | May 3, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.