Triple
T36323918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassie |
E894407
|
entity |
| Predicate | writerOfWorkAppearedIn |
P110113
|
FINISHED |
| Object | Alex Garland |
—
|
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: Alex Garland | Statement: [Cassie, writerOfWorkAppearedIn, Alex Garland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writerOfWorkAppearedIn Context triple: [Cassie, writerOfWorkAppearedIn, Alex Garland]
-
A.
authorOfWorkAppearingIn
chosen
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
-
B.
creatorOfWorkAppearedIn
Indicates that a person is the creator (e.g., author, artist, director) of a work in which a given entity appeared.
-
C.
workWriterOfWorkAppearedIn
Indicates that a work is written by an author whose work appeared in a particular publication or context.
-
D.
workAppearedInWriter
Indicates that a particular work by a writer was published or featured in a specific writer (e.g., as part of their collected works or authored output).
-
E.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.