Triple
T7894300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC Game Pass |
E183308
|
entity |
| Predicate | trialOption |
P79618
|
FINISHED |
| Object | occasionally offers introductory pricing or trials |
—
|
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: occasionally offers introductory pricing or trials | Statement: [PC Game Pass, trialOption, occasionally offers introductory pricing or trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialOption Context triple: [PC Game Pass, trialOption, occasionally offers introductory pricing or trials]
-
A.
trialName
Indicates the designated name or title assigned to a specific trial.
-
B.
trialAfter
Indicates that one trial or legal proceeding occurs subsequent to another in time or sequence.
-
C.
trial
Indicates that an entity is the subject of a legal or formal judicial proceeding to determine guilt, liability, or resolution of a dispute.
-
D.
trialMode
Indicates that an entity is operating in a temporary, limited-capability trial state rather than in full or permanent mode.
-
E.
trialFormat
Indicates the specific structure, rules, or procedural setup under which a trial or experimental process is conducted.
- F. None of above. chosen
Provenance (4 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a15a7e88190a05474844817e5d2 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 5:01 p.m.