Triple
T27811740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Bots |
E702534
|
entity |
| Predicate | hasMerchFeature |
P3585
|
FINISHED |
| Object | remote control movement |
—
|
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: remote control movement | Statement: [Spider-Bots, hasMerchFeature, remote control movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMerchFeature Context triple: [Spider-Bots, hasMerchFeature, remote control movement]
-
A.
hasExtensiveMerchandise
Indicates that an entity offers a large and varied range of merchandise or products.
-
B.
hasMerchandiseTieIn
Indicates that one entity has a commercial or promotional product or line (merchandise) that is directly tied to, branded with, or derived from another entity.
-
C.
fanMerchandiseAvailable
Indicates that merchandise related to a fan or fandom is available for purchase or acquisition.
-
D.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
E.
hasMarketingElement
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 27, 2026, 5:43 p.m.