Triple
T33093513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slinky |
E846845
|
entity |
| Predicate | hasRegisteredTrademark |
P10471
|
FINISHED |
| Object | Slinky |
E846845
|
NE 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: Slinky | Statement: [Slinky, hasRegisteredTrademark, Slinky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegisteredTrademark Context triple: [Slinky, hasRegisteredTrademark, Slinky]
-
A.
sharesTrademark
Indicates that two or more entities use or are associated with the same trademark.
-
B.
trademark
chosen
Indicates that one entity legally owns and uses a distinctive sign, name, or symbol to identify and distinguish its goods or services from those of others.
-
C.
hasNoTrademarkGrant
Indicates that no legal rights or permissions have been granted to use a trademark in connection with the referenced entity or activity.
-
D.
hostTrademark
Indicates that one entity serves as the host or platform on which another entity’s trademark is presented, displayed, or made available.
-
E.
hasTradeName
Indicates that a product, substance, or entity is known or marketed under a specific commercial or brand name.
- F. None of above.
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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a034540e37c819087a5c75c559323d8 |
completed | May 12, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f028a3b48190aa3d9f56a248d051 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a0344e26fec8190867227f9692e92df |
completed | May 12, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1:26 a.m.