Triple
T994475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney+ |
E21464
|
entity |
| Predicate | hasServiceTier |
P849
|
FINISHED |
| Object | ad-supported plan |
—
|
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: ad-supported plan | Statement: [Disney+, hasServiceTier, ad-supported plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceTier Context triple: [Disney+, hasServiceTier, ad-supported plan]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
hasMembershipBase
Indicates that an entity possesses or is associated with a foundational group or set of members that form its membership base.
-
D.
hasVIPTerminal
Indicates that one entity possesses or provides access to a VIP (very important person) terminal associated with another entity.
-
E.
hasMembershipProgram
Indicates that an entity offers or participates in a structured membership program, typically providing special access, benefits, or services to enrolled members.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c75de88190bf7fec7a053f7a90 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2af071c819086c374a16307dfe0 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.