Triple
T31983586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "And away we go!" |
E816654
|
entity |
| Predicate | signatureLineOf |
P173077
|
FINISHED |
| Object | Jackie Gleason |
—
|
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: Jackie Gleason | Statement: ["And away we go!", signatureLineOf, Jackie Gleason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureLineOf Context triple: ["And away we go!", signatureLineOf, Jackie Gleason]
-
A.
signatureLine
Indicates that an entity serves as a designated place or line where a signature is written or recorded.
-
B.
isSignatureLineOf
Indicates that a given line or field serves as the designated place for a signature within a specific document or form.
-
C.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signatureConcept
Indicates that one concept is the defining or characteristic idea that most distinctly represents or identifies another concept.
-
E.
signatureExample
Indicates that an entity serves as an illustrative or representative instance of a particular signature, pattern, or formal specification.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3ad0d0481909f2cf7d931a3a418 |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:12 a.m.