Triple
T9879089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bootylicious |
E240154
|
entity |
| Predicate | hasTitleWordOrigin |
P8466
|
FINISHED |
| Object | blend of "booty" and "delicious" |
—
|
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: blend of "booty" and "delicious" | Statement: [Bootylicious, hasTitleWordOrigin, blend of "booty" and "delicious"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleWordOrigin Context triple: [Bootylicious, hasTitleWordOrigin, blend of "booty" and "delicious"]
-
A.
hasTitleEtymology
chosen
Indicates that the origin or derivation of a title is based on, or explained by, another term, name, or linguistic source.
-
B.
etymologyTheme
Indicates that something (such as a word, name, or term) has its origin, derivation, or linguistic history related to a particular theme, source, or conceptual basis.
-
C.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
D.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
E.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb4135c108190b3330e929509699d |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:37 p.m.