Triple
T523256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ye |
E10862
|
entity |
| Predicate | coverArtText |
P15271
|
FINISHED |
| Object | I hate being Bi-Polar its awesome |
—
|
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: I hate being Bi-Polar its awesome | Statement: [Ye, coverArtText, I hate being Bi-Polar its awesome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverArtText Context triple: [Ye, coverArtText, I hate being Bi-Polar its awesome]
-
A.
artworkType
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
-
B.
artForm
Indicates the type or category of artistic expression that characterizes or defines something (e.g., painting, music, dance).
-
C.
hasIllustrations
Indicates that an entity includes or is accompanied by visual illustrations.
-
D.
hasIllustrationsBy
Indicates that one entity (such as a work or publication) includes illustrations that were created by another entity (the illustrator).
-
E.
obverseDepiction
Indicates that one entity is depicted on the obverse (front) side of another, such as the front face of a coin or medal.
- F. None of above. chosen
Provenance (4 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b4f01881908b408357ff113308 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0f73af88190bc8f00c2047cc8b8 |
completed | Feb. 28, 2026, 1:43 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.