Triple
T37129002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puppy Co. |
E919466
|
entity |
| Predicate | usesInFictionalPlotDevice |
P105687
|
FINISHED |
| Object | secret scheme |
—
|
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: secret scheme | Statement: [Puppy Co., usesInFictionalPlotDevice, secret scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInFictionalPlotDevice Context triple: [Puppy Co., usesInFictionalPlotDevice, secret scheme]
-
A.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
B.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
C.
usedInFictionalWork
chosen
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
-
D.
worksUnderInFiction
Indicates that, within a fictional context or narrative, one character or entity is hierarchically subordinate to and takes direction from another.
-
E.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.