Triple
T17904127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angus Cloud |
E447656
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Cloud |
E943084
|
NE 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 | Statement: [Angus Cloud, familyName, Cloud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cloud Context triple: [Angus Cloud, familyName, Cloud]
-
A.
Cloud
Cloud is the fan club associated with the artist or group known as Rain.
-
B.
Cloud
chosen
Cloud is a surname most notably associated with American politician Michael Cloud.
-
C.
CLOUD
CLOUD is a CERN experiment that studies how cosmic rays and atmospheric aerosols influence cloud formation and, consequently, Earth's climate.
-
D.
Cloud computing
Cloud computing is a model of delivering computing resources—such as servers, storage, databases, networking, and software—over the internet on demand, typically with pay-as-you-go pricing.
-
E.
Cloud Controller
Cloud Controller is the central Cloud Foundry component responsible for managing application lifecycles, including deployment, scaling, and routing of apps on the platform.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9a9cfc8190879fc36dfdeb562b |
completed | April 19, 2026, 9:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a031b2bc9bc819096bf2d2f2a94910b |
completed | May 12, 2026, 12:20 p.m. |
Created at: April 10, 2026, 10:19 a.m.