Triple
T36778441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bottom Bitch |
E908698
|
entity |
| Predicate | featuresElementFrom |
P205042
|
FINISHED |
| Object | What’s My Age Again? |
E399224
|
NE 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: What’s My Age Again? | Statement: [Bottom Bitch, featuresElementFrom, What’s My Age Again?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresElementFrom Context triple: [Bottom Bitch, featuresElementFrom, What’s My Age Again?]
-
A.
featuresElementSystem
Indicates that a system includes or incorporates a particular element as one of its constituent parts or components.
-
B.
featuredElement
Indicates that one element is highlighted or given special prominence relative to others in a given context.
-
C.
featuresLiveElements
Indicates that something includes or contains elements that are dynamic, interactive, or capable of real-time change or behavior.
-
D.
featuresCollectionFrom
Indicates that one entity serves as the source or origin from which a collection of features is derived or obtained for another entity.
-
E.
featuresRecurringElement
Indicates that something includes an element, motif, or component that appears repeatedly over time or across multiple instances.
- F. None of above. chosen
Provenance (5 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dde5748f4819081f004d2f004fc36 |
completed | June 26, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.