Triple
T18254826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wish |
E437195
|
entity |
| Predicate | merchantType |
P131041
|
FINISHED |
| Object | third-party sellers |
—
|
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: third-party sellers | Statement: [Wish, merchantType, third-party sellers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: merchantType Context triple: [Wish, merchantType, third-party sellers]
-
A.
commercialCategory
Indicates the type of commercial classification or business category under which an entity or transaction is grouped.
-
B.
isCommercialFacility
Indicates that a facility is used primarily for commercial or business-related activities or services.
-
C.
commercialCustomer
Indicates a relationship where an entity purchases or uses goods or services from another entity for commercial or business purposes.
-
D.
commercialAgency
Indicates a relationship where one party acts as a commercial agent, authorized to promote, negotiate, or conclude business transactions on behalf of another party.
-
E.
commercialService
Indicates a relationship where one entity provides a paid, profit-oriented service to another entity.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd84b3a481908bbc1a5e5034d397 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.