Triple
T33532568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitch |
E858833
|
entity |
| Predicate | hasExplicitWordInTitle |
P85554
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bitch, hasExplicitWordInTitle, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExplicitWordInTitle Context triple: [Bitch, hasExplicitWordInTitle, yes]
-
A.
containsExplicitWordInTitle
chosen
Indicates that the title of an item includes at least one word that is considered explicit or profane.
-
B.
hasExplicitTitle
Indicates that an entity is associated with a clearly specified, formally stated title rather than an implicit or inferred one.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
E.
hasTitleInName
Indicates that an entity’s name explicitly includes a specified title as part of it.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:39 a.m.