Triple
T29658493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pet Society Vacation |
E750336
|
entity |
| Predicate | hasVirtualGoods |
P37743
|
FINISHED |
| Object | decorative items |
—
|
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: decorative items | Statement: [Pet Society Vacation, hasVirtualGoods, decorative items]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVirtualGoods Context triple: [Pet Society Vacation, hasVirtualGoods, decorative items]
-
A.
hasFictionalProduct
Indicates a relationship where one entity features, offers, or includes a product that exists only in fiction or an imagined context.
-
B.
hasVirtualExperience
Indicates that one entity possesses or has participated in a virtual or digitally simulated experience related to another entity.
-
C.
hasGoodsServices
Indicates that one entity provides, offers, or is associated with specific goods or services in relation to another entity.
-
D.
hasInAppPurchases
chosen
Indicates that an application offers additional content, features, or services that users can buy from within the app itself.
-
E.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 6:57 p.m.