Triple
T22768954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerry Co. toy company |
E563200
|
entity |
| Predicate | hasFictionalProductType |
P117060
|
FINISHED |
| Object | toys |
—
|
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: toys | Statement: [Jerry Co. toy company, hasFictionalProductType, toys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalProductType Context triple: [Jerry Co. toy company, hasFictionalProductType, toys]
-
A.
hasFictionalProduct
Indicates a relationship where one entity features, offers, or includes a product that exists only in fiction or an imagined context.
-
B.
hasFictionalType
chosen
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
C.
hasFictionalProductionType
Indicates that an entity is associated with a specific type or category of fictional production (such as a genre, format, or style).
-
D.
hasFictionalBusinessType
Indicates that an entity is associated with a type or category of fictional business it operates or represents.
-
E.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b59c9cc8190a6edd68f3209a672 |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:27 p.m.