Triple
T20762442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Little Pony toys |
E511004
|
entity |
| Predicate | hasPlayPattern |
P141428
|
FINISHED |
| Object | imaginative play |
—
|
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: imaginative play | Statement: [My Little Pony toys, hasPlayPattern, imaginative play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayPattern Context triple: [My Little Pony toys, hasPlayPattern, imaginative play]
-
A.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
B.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
C.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
D.
hasPlanningPattern
Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
-
E.
trackPattern
Indicates that one entity follows, monitors, or records the behavior or state of another according to a defined pattern or sequence.
- F. None of above. chosen
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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24a154c8190a9062923308d2411 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:35 p.m.