Triple
T31710844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Heart Hospital |
E809311
|
entity |
| Predicate | internCharacter |
P193317
|
FINISHED |
| Object | John "J.D." Dorian |
—
|
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: John "J.D." Dorian | Statement: [Sacred Heart Hospital, internCharacter, John "J.D." Dorian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internCharacter Context triple: [Sacred Heart Hospital, internCharacter, John "J.D." Dorian]
-
A.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
B.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
C.
semiAutobiographicalCharacter
Indicates that a character is based partly on the real-life experiences, personality, or identity of its creator or author, but is not a fully direct self-portrayal.
-
D.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
E.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
- F. None of above. chosen
Provenance (4 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 30, 2026, 11:15 p.m.