Triple
T18258076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go.com |
E437267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | online services brand |
C23824
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: online services brand Context triple: [Go.com, instanceOf, online services brand]
-
A.
online service brand
chosen
An online service brand is a digital-first identity that represents and differentiates a company’s web-based products or services through consistent visual, verbal, and experiential elements across online touchpoints.
-
B.
online educational content brand
An online educational content brand is a digitally focused identity that consistently creates, curates, and distributes learning materials to a targeted audience under a recognizable name, style, and value proposition.
-
C.
global brand
A global brand is a widely recognized product or company identity that maintains consistent values, messaging, and visual elements across multiple countries and cultures while adapting selectively to local markets.
-
D.
digital services organization
A digital services organization is an entity that designs, builds, and operates technology-enabled solutions—such as software platforms, applications, and online services—to deliver value and outcomes for customers and stakeholders.
-
E.
soft brand
A soft brand is a hotel or hospitality affiliation model that allows independently owned properties to retain their unique identity and operations while benefiting from a larger brand’s distribution, loyalty programs, and marketing support.
- F. None of above.
Provenance (1 batch)
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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.