Triple
T14375787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOW (streaming service) |
E356469
|
entity |
| Predicate | hasPassType |
P42000
|
FINISHED |
| Object | Entertainment Membership |
—
|
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: Entertainment Membership | Statement: [NOW (streaming service), hasPassType, Entertainment Membership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassType Context triple: [NOW (streaming service), hasPassType, Entertainment Membership]
-
A.
hasPass
Indicates that an entity possesses or has been granted a pass, such as a ticket, permit, or authorization to access something.
-
B.
passType
chosen
Indicates the type or category of a pass that is involved in or assigned within the relationship between entities.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasMatchCardType
Indicates that two or more items share the same card type or that an item is associated with a specific matching card type.
-
E.
hasTypeOfCredit
Indicates that an entity is associated with or characterized by a specific type or category of credit.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900949fc81909be0da1734c46645 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.