Triple
T31649626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Finlay's Casebook |
E807680
|
entity |
| Predicate | hasCountryDoctorProtagonist |
P127445
|
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: [Dr. Finlay's Casebook, hasCountryDoctorProtagonist, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryDoctorProtagonist Context triple: [Dr. Finlay's Casebook, hasCountryDoctorProtagonist, true]
-
A.
hasDoctorActor
Indicates that a doctor participates as an acting agent in the specified event or relationship.
-
B.
hasDoctorCharacter
chosen
Indicates that an entity includes or features a character whose role or profession is that of a doctor.
-
C.
hasSeriesDoctor
Indicates that a particular doctor is associated with or responsible for a given series (such as a TV show, book series, or medical series).
-
D.
portrayedDoctorBy
Indicates that one entity served in the role of portraying a doctor character associated with another entity (such as a show, film, or franchise).
-
E.
featuredDoctor
Indicates that a particular doctor is highlighted or promoted as a primary or notable medical professional in a given context.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a030713bd2881908bcc69e7d1e9fd09 |
completed | May 12, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a0304c29abc819085ffd17ab9a8c844 |
completed | May 12, 2026, 10:45 a.m. |
Created at: April 30, 2026, 10:52 p.m.