Triple
T36486184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASSIOPE |
E898937
|
entity |
| Predicate | dataApplications |
P106222
|
FINISHED |
| Object | broadband data delivery |
—
|
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: broadband data delivery | Statement: [CASSIOPE, dataApplications, broadband data delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataApplications Context triple: [CASSIOPE, dataApplications, broadband data delivery]
-
A.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another entity.
-
B.
aplicación
chosen
Indicates that one entity is the use or implementation of another entity for a specific purpose or function.
-
C.
relatedApplication
Indicates that one application has a defined connection or association with another application, such as dependency, complementarity, or functional linkage.
-
D.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
E.
applicationRange
Indicates the scope or extent within which something (such as a rule, function, or process) is validly applied or operates.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.