Triple
T9788066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al’s Toy Barn |
E237536
|
entity |
| Predicate | hasPromotionalDisplays |
P5950
|
FINISHED |
| Object | Buzz Lightyear display |
—
|
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: Buzz Lightyear display | Statement: [Al’s Toy Barn, hasPromotionalDisplays, Buzz Lightyear display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromotionalDisplays Context triple: [Al’s Toy Barn, hasPromotionalDisplays, Buzz Lightyear display]
-
A.
hasMainPromotion
Indicates that an entity is associated with its primary or most prominent promotional offer or campaign.
-
B.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to another entity.
-
C.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
D.
hasCoPromotionPartner
Indicates a relationship where two entities collaborate as partners to jointly promote a product, service, or initiative.
-
E.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda2131164819099e8644e40a3cab6 |
completed | April 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.