Triple
T21842303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby Sparks |
E539283
|
entity |
| Predicate | featuresCharacterWhoIsWriter |
P93957
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ruby Sparks, featuresCharacterWhoIsWriter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterWhoIsWriter Context triple: [Ruby Sparks, featuresCharacterWhoIsWriter, true]
-
A.
screenwriterOfWorkFeaturingCharacter
Indicates that one entity is the screenwriter of a work in which the other entity appears as a character.
-
B.
screenwritersCharacterOf
Indicates that one or more screenwriters are responsible for creating or writing a particular character.
-
C.
screenwriterCharacterRelatedTo
Indicates a relationship where a screenwriter is connected to a character, such as by having created, written for, or otherwise developed that character in a screenplay.
-
D.
screenwriterCharacterFunction
Indicates that a screenwriter is responsible for creating, defining, or shaping a character’s role and function within a screenplay or script.
-
E.
featuresCharacterWith
chosen
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7acb17c81908c0de0afac5a9fa7 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.