Triple
T27587080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rackspace |
E699711
|
entity |
| Predicate | coreValueProposition |
P25020
|
FINISHED |
| Object | Fanatical Support |
—
|
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: Fanatical Support | Statement: [Rackspace, coreValueProposition, Fanatical Support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreValueProposition Context triple: [Rackspace, coreValueProposition, Fanatical Support]
-
A.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
B.
primaryBenefit
chosen
Indicates that one entity serves as the main or most important advantage, gain, or positive outcome associated with another entity.
-
C.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
D.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
E.
businessModelAdvocacy
Indicates that an entity promotes, supports, or argues in favor of a particular business model or way of generating value.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6301b49b48190ba04ed98a25cb7d6 |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:04 p.m.