Triple
T31228949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Too Close for Comfort |
E796223
|
entity |
| Predicate | laterSyndicationTitle |
P150350
|
FINISHED |
| Object | Too Close for Comfort |
—
|
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: Too Close for Comfort | Statement: [Too Close for Comfort, laterSyndicationTitle, Too Close for Comfort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSyndicationTitle Context triple: [Too Close for Comfort, laterSyndicationTitle, Too Close for Comfort]
-
A.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
B.
laterAdaptationName
Indicates that the object is the name of a later adaptation derived from or based on the subject.
-
C.
laterAiredInSyndication
chosen
Indicates that the subject was broadcast at a later time in syndication than the object.
-
D.
ledByTitle
Indicates that an organization, group, or initiative is headed or directed by a person holding a specified leadership title.
-
E.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: April 29, 2026, 9:10 p.m.