Triple
T19450869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Company Store at Infinite Loop |
E486609
|
entity |
| Predicate | hasTypeOfProducts |
P90900
|
FINISHED |
| Object | consumer electronics accessories |
—
|
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: consumer electronics accessories | Statement: [Apple Company Store at Infinite Loop, hasTypeOfProducts, consumer electronics accessories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfProducts Context triple: [Apple Company Store at Infinite Loop, hasTypeOfProducts, consumer electronics accessories]
-
A.
hasProduct
Indicates that an entity possesses, offers, or is associated with a particular product.
-
B.
hasListedProductType
Indicates that an entity has a product associated with it that is categorized under a specific listed product type.
-
C.
typeOfProducts
chosen
Indicates the kinds or categories of products that are associated with or offered by an entity.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasProductUser
Indicates that a product is associated with or used by a particular user.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.