Triple
T1400306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SkyPod observation deck |
E30763
|
entity |
| Predicate | isMarketedAs |
P5087
|
FINISHED |
| Object | premium viewing experience |
—
|
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: premium viewing experience | Statement: [SkyPod observation deck, isMarketedAs, premium viewing experience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMarketedAs Context triple: [SkyPod observation deck, isMarketedAs, premium viewing experience]
-
A.
marketedFor
chosen
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
B.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
C.
originalMarketingName
Indicates the original marketing or brand name under which an entity (such as a product or service) was first promoted or sold.
-
D.
marketedBy
Indicates that one entity is promoted, advertised, or commercially presented to customers by another entity.
-
E.
alsoSoldAs
Indicates that one item is marketed or available under an alternative name, label, or product identity.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39c4c148190997150996ca26a99 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.