Triple
T2532435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porky Pig |
E56191
|
entity |
| Predicate | signaturePhrase |
P19775
|
FINISHED |
| Object | Th-th-th-that's all folks! |
—
|
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: Th-th-th-that's all folks! | Statement: [Porky Pig, signaturePhrase, Th-th-th-that's all folks!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signaturePhrase Context triple: [Porky Pig, signaturePhrase, Th-th-th-that's all folks!]
-
A.
signaturePhraseAssociated
chosen
Indicates that a characteristic or frequently used phrase is associated with a particular entity as its recognizable or defining expression.
-
B.
signText
Indicates that a sign bears or displays a particular textual content.
-
C.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signatureLanguage
Indicates the language in which a signature (e.g., on a document or agreement) is written or expressed.
-
E.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd279cf108190b03fb6e0265f39d9 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.