Triple
T35142803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cow in the Meadow Goes Moo |
E1014740
|
entity |
| Predicate | isFictionalWorkWithinWork |
P182578
|
FINISHED |
| Object | Friends |
—
|
NE NERFINISHED |
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: Friends | Statement: [The Cow in the Meadow Goes Moo, isFictionalWorkWithinWork, Friends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFictionalWorkWithinWork Context triple: [The Cow in the Meadow Goes Moo, isFictionalWorkWithinWork, Friends]
-
A.
isForFictionalWork
Indicates that something is intended to be used in, associated with, or specifically created for a fictional work.
-
B.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
C.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
D.
worksWithInFiction
Indicates that two fictional characters are depicted as collaborating, interacting, or being associated with each other within a narrative work.
-
E.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.