Triple
T16543978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Huntley–Brinkley Report |
E401891
|
entity |
| Predicate | signOffPhrase |
P65658
|
FINISHED |
| Object | Good night, Chet |
—
|
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: Good night, Chet | Statement: [The Huntley–Brinkley Report, signOffPhrase, Good night, Chet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signOffPhrase Context triple: [The Huntley–Brinkley Report, signOffPhrase, Good night, Chet]
-
A.
signaturePhraseAssociated
Indicates that a characteristic or frequently used phrase is associated with a particular entity as its recognizable or defining expression.
-
B.
hasSignaturePhrase
chosen
Indicates that an entity (such as a person or character) is associated with a distinctive, repeatedly used phrase that is characteristically theirs.
-
C.
signText
Indicates that a sign bears or displays a particular textual content.
-
D.
signGivenBy
Indicates that a sign (such as a signal, gesture, or indication) is produced or provided by one entity to another.
-
E.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455fab34819086c77ff45b85f5db |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.