Triple
T14653899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space (Canadian TV channel) |
E344059
|
entity |
| Predicate | formerLogoIncludes |
P27117
|
FINISHED |
| Object | stylized word "SPACE" |
—
|
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: stylized word "SPACE" | Statement: [Space (Canadian TV channel), formerLogoIncludes, stylized word "SPACE"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLogoIncludes Context triple: [Space (Canadian TV channel), formerLogoIncludes, stylized word "SPACE"]
-
A.
hasFormerLogo
chosen
Indicates that an entity is associated with a logo it used in the past but no longer uses.
-
B.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
C.
hasLogoShape
Indicates that an entity’s logo is characterized by or takes the form of a specified geometric or visual shape.
-
D.
logoUsedBy
Indicates that a particular logo is employed or displayed by a specific entity as part of its identity, branding, or representation.
-
E.
logoUsedIn
Indicates that a particular logo is employed or displayed within a specified context, medium, or artifact.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb518f7dc8190877997ea4cd3eed2 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.