Triple
T28549019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Let's Celebrate!" |
E722827
|
entity |
| Predicate | typicalPunctuation |
P19764
|
FINISHED |
| Object | exclamation mark |
—
|
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: exclamation mark | Statement: ["Let's Celebrate!", typicalPunctuation, exclamation mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPunctuation Context triple: ["Let's Celebrate!", typicalPunctuation, exclamation mark]
-
A.
punctuation
Indicates the presence, type, or pattern of punctuation marks used within or between textual elements.
-
B.
punctuationVariant
Indicates a relationship where one written form is a variant of another that differs only in punctuation.
-
C.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
D.
titlePunctuation
chosen
Indicates that a title includes specific punctuation marks or follows a particular punctuation pattern.
-
E.
typicalStopPattern
Indicates the usual or most common sequence or arrangement of stops associated with an entity’s operation or route.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: April 28, 2026, 3:41 a.m.