Triple
T38629696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Exploits of Elaine |
E937415
|
entity |
| Predicate | screenCharacterOrigin |
P90667
|
FINISHED |
| Object | Craig Kennedy detective stories |
—
|
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: Craig Kennedy detective stories | Statement: [The Exploits of Elaine, screenCharacterOrigin, Craig Kennedy detective stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenCharacterOrigin Context triple: [The Exploits of Elaine, screenCharacterOrigin, Craig Kennedy detective stories]
-
A.
screenCharacterBy
Indicates a relationship where one entity evaluates or selects characters according to certain criteria or standards.
-
B.
characterSetOrigin
Indicates the source or defining system from which a particular character set is derived or specified.
-
C.
screenWriterCharacterOf
Indicates that a person serves as the screenwriter responsible for writing the character or the character’s role in a screenplay or film.
-
D.
characterOrigin
Indicates the source, background, or initial context from which a character originates.
-
E.
originOfCharacter
chosen
Indicates the source or place from which a character originates or is created.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.