Triple
T31313994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida!!! |
E798537
|
entity |
| Predicate | titleIncludesPunctuation |
P19764
|
FINISHED |
| Object | three exclamation marks |
—
|
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: three exclamation marks | Statement: [Florida!!!, titleIncludesPunctuation, three exclamation marks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleIncludesPunctuation Context triple: [Florida!!!, titleIncludesPunctuation, three exclamation marks]
-
A.
titlePunctuation
chosen
Indicates that a title includes specific punctuation marks or follows a particular punctuation pattern.
-
B.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
C.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
-
D.
hasTitlePun
Indicates that an entity’s title involves a pun or wordplay, typically combining multiple meanings or sounds for humorous or clever effect.
-
E.
titleContainsPronoun
Indicates that the title of an entity includes at least one pronoun.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 29, 2026, 9:15 p.m.