Triple
T32617226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxeia |
E833819
|
entity |
| Predicate | wasOfferedForSale |
P174938
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Oxeia, wasOfferedForSale, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOfferedForSale Context triple: [Oxeia, wasOfferedForSale, 2010s]
-
A.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
B.
soldAs
Indicates that one entity is marketed, offered, or presented to others under the name, form, or role of another entity.
-
C.
soldAt
Indicates that a product or item is offered for sale at a particular location, venue, or outlet.
-
D.
areSoldThrough
Indicates that items or services are made available to buyers via a particular sales channel, intermediary, or distribution method.
-
E.
soldWith
Indicates that one item is sold together with another item as part of the same transaction or offer.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 1:06 a.m.