Triple
T11404029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penelope Sycamore |
E270188
|
entity |
| Predicate | workFormatAppearedIn |
P37319
|
FINISHED |
| Object | 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: play | Statement: [Penelope Sycamore, workFormatAppearedIn, play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFormatAppearedIn Context triple: [Penelope Sycamore, workFormatAppearedIn, play]
-
A.
workWriterOfWorkAppearedIn
Indicates that a work is written by an author whose work appeared in a particular publication or context.
-
B.
settingOfWorkAppearsIn
Indicates that a particular place, time, or environment serves as the setting within which a given creative work’s events or narrative occur.
-
C.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
D.
formatOfWorks
chosen
Indicates the specific medium, layout, or structural form in which works are created, presented, or published.
-
E.
settingOfWorkFeaturedIn
Indicates that a place or environment serves as the primary setting where the events of a creative work take place.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014ab46881909fa1d425926c617b |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.