Triple
T35851916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reagan Brinkley |
E1036382
|
entity |
| Predicate | createdByCharacterCreator |
P40162
|
FINISHED |
| Object | Emily Spivey |
—
|
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: Emily Spivey | Statement: [Reagan Brinkley, createdByCharacterCreator, Emily Spivey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByCharacterCreator Context triple: [Reagan Brinkley, createdByCharacterCreator, Emily Spivey]
-
A.
createdByCharacterRole
Indicates that something (such as a work, item, or event) was brought into existence or produced by an entity acting in a specific character role.
-
B.
createdByCharacterInUniverse
Indicates that something (such as a work, object, or concept) was created by a specific character within a particular fictional universe.
-
C.
createdByCharacterGroup
Indicates that something was created collectively by a specific group of characters acting together.
-
D.
creatorOfCharacter
chosen
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
E.
createdArtworkForCharacter
Indicates that an artwork was created specifically for, or depicting, a particular character.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: May 3, 2026, 4:06 p.m.