Triple
T32363889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ***Flawless |
E826936
|
entity |
| Predicate | containsChant |
P194256
|
FINISHED |
| Object | I woke up like this |
—
|
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 woke up like this | Statement: [***Flawless, containsChant, I woke up like this]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsChant Context triple: [***Flawless, containsChant, I woke up like this]
-
A.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
B.
hasChantLikeChorus
Indicates that one element features or is characterized by a chorus section that is chant-like in style or delivery.
-
C.
usedAsChant
Indicates that something (typically a phrase, text, or sound) is employed as a chant in a ritual, performance, or repetitive vocal practice.
-
D.
hasChantLikeSections
chosen
Indicates that something contains portions that resemble or function like chants in style, rhythm, or delivery.
-
E.
hasChantingStyle
Indicates that an entity is associated with or characterized by a particular style or manner of chanting.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 1, 2026, 12:50 a.m.