Triple
T29630508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Al Franken Show |
E755557
|
entity |
| Predicate | hasCallInFormat |
P194516
|
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: [The Al Franken Show, hasCallInFormat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallInFormat Context triple: [The Al Franken Show, hasCallInFormat, true]
-
A.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
B.
hasCallingPattern
Indicates that one entity uses or invokes another according to a specific, characteristic pattern of calls or interactions.
-
C.
hasCall
Indicates that one entity initiates or participates in a telephone or voice communication with another entity.
-
D.
hasCallLine
Indicates that there is a specific telephone or communication line associated with or used for a particular call.
-
E.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
| PDg | Predicate description generation | batch_69fd783e9e5c819087dec7fefa03700d |
completed | May 8, 2026, 5:44 a.m. |
Created at: April 28, 2026, 6:40 p.m.