Triple
T21951838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Express |
E542087
|
entity |
| Predicate | availableForPurchase |
P110535
|
FINISHED |
| Object | online |
—
|
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: online | Statement: [Universal Express, availableForPurchase, online]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableForPurchase Context triple: [Universal Express, availableForPurchase, online]
-
A.
canBePurchased
chosen
Indicates that one entity is available to be bought or acquired in exchange for payment by another entity.
-
B.
hasInAppPurchases
Indicates that an application offers additional content, features, or services that users can buy from within the app itself.
-
C.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
D.
eligiblePurchasers
Indicates that certain entities are permitted or qualified to make a particular purchase under specified rules or conditions.
-
E.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of another entity.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243c84d4819097f5a93b128f024b |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:58 p.m.