Triple
T5355532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprint Corporation |
E102679
|
entity |
| Predicate | notableMarketingElement |
P60713
|
FINISHED |
| Object | yellow color scheme |
—
|
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: yellow color scheme | Statement: [Sprint Corporation, notableMarketingElement, yellow color scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMarketingElement Context triple: [Sprint Corporation, notableMarketingElement, yellow color scheme]
-
A.
notableBrandElement
chosen
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
notablePromotion
Indicates that an entity has received a significant or distinguished promotion in status, rank, or position.
-
C.
notableMarketPositioning
Indicates that an entity holds a distinctive or strategically significant position within a particular market or competitive landscape.
-
D.
notableProduct
Indicates that a product is especially significant, prominent, or well-known in relation to the associated entity.
-
E.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd862f0ea48190bec78690ab3bee51 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.