Triple
T3169740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | This Can't Be Love |
E66297
|
entity |
| Predicate | usedAsJazzStandard |
P46714
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [This Can't Be Love, usedAsJazzStandard, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsJazzStandard Context triple: [This Can't Be Love, usedAsJazzStandard, true]
-
A.
becameStandardFor
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
-
B.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
E.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada64917e08190bf0466d2c5e43790 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada20880e481908ecac09d49b1f1c3 |
completed | March 8, 2026, 4:21 p.m. |
Created at: March 8, 2026, 3:06 p.m.