Triple
T20953665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Art |
E516042
|
entity |
| Predicate | refrainLine |
P32220
|
FINISHED |
| Object | The art of losing isn’t hard to master. |
—
|
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: The art of losing isn’t hard to master. | Statement: [One Art, refrainLine, The art of losing isn’t hard to master.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refrainLine Context triple: [One Art, refrainLine, The art of losing isn’t hard to master.]
-
A.
refrainText
chosen
Indicates that a piece of text functions as the recurring refrain or repeated line within a larger work, such as a song or poem.
-
B.
refrain
Indicates that an entity deliberately holds back from performing a particular action or behavior.
-
C.
refrainTranslation
Indicates that one expression is a translation of the repeated or recurring part (refrain) of another expression, typically in a different language.
-
D.
refrainFunction
Indicates that an entity performs the function or role of a refrain, typically recurring or repeating within a larger structure.
-
E.
refrainCount
Indicates the number of times a particular refrain or repeated segment occurs within a larger sequence or structure.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fae154a481909f235165a46d0910 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:28 p.m.