Triple
T16678087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B.U.D.D.Y. |
E405264
|
entity |
| Predicate | titlePunctuationStyle |
P81918
|
FINISHED |
| Object | period-separated letters |
—
|
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: period-separated letters | Statement: [B.U.D.D.Y., titlePunctuationStyle, period-separated letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titlePunctuationStyle Context triple: [B.U.D.D.Y., titlePunctuationStyle, period-separated letters]
-
A.
titlePunctuation
Indicates that a title includes specific punctuation marks or follows a particular punctuation pattern.
-
B.
titleStylization
chosen
Indicates how the written form of a title is stylistically presented, such as through capitalization, spacing, punctuation, or special formatting.
-
C.
titleStyleInFull
Indicates that the specified title is presented in its complete, unabridged form, including all stylistic elements or formatting.
-
D.
punctuation
Indicates the presence, type, or pattern of punctuation marks used within or between textual elements.
-
E.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6db3488190b56e13ddb69ef8f1 |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.