Triple
T28327382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainbow Crafts |
E717448
|
entity |
| Predicate | roleInPlayDohHistory |
P133782
|
FINISHED |
| Object | original manufacturer |
—
|
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: original manufacturer | Statement: [Rainbow Crafts, roleInPlayDohHistory, original manufacturer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPlayDohHistory Context triple: [Rainbow Crafts, roleInPlayDohHistory, original manufacturer]
-
A.
roleInPerformanceHistory
Indicates the specific role or function an entity held within a particular performance, as recorded in a historical context.
-
B.
rolHistórico
chosen
Indicates the historical role or function that one entity has played in relation to another over time.
-
C.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
D.
storesHistory
Indicates that an entity retains or records past states, events, or changes over time related to another entity or process.
-
E.
operationalHistory
Indicates the record of how something has been used, functioned, or operated over time, including its past activities and events.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 28, 2026, 12:29 a.m.