Triple
T36486219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASSIOPE |
E898938
|
entity |
| Predicate | hasCommunicationsPayload |
P90112
|
FINISHED |
| Object | Cascade |
E259998
|
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: Cascade | Statement: [CASSIOPE, hasCommunicationsPayload, Cascade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunicationsPayload Context triple: [CASSIOPE, hasCommunicationsPayload, Cascade]
-
A.
hasCommunicationType
Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
-
B.
hasPayload
chosen
Indicates that one entity carries, contains, or is equipped with another entity as its payload.
-
C.
hasCommunicationAccess
Indicates that one entity is able to communicate with, or use a communication channel or service provided by, another entity.
-
D.
hasCommunicationClass
Indicates that one entity is assigned to, or associated with, a particular category or class of communication.
-
E.
hasCommunicationCodeType
Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
- F. None of above.
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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfe0b8208190b6b51c7b658a0409 |
completed | June 23, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.