Triple
T1351833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Made to Love |
E28898
|
entity |
| Predicate | featuresProminentElement |
P7153
|
FINISHED |
| Object | emotive vocals |
—
|
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: emotive vocals | Statement: [Made to Love, featuresProminentElement, emotive vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProminentElement Context triple: [Made to Love, featuresProminentElement, emotive vocals]
-
A.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
B.
keyFeature
chosen
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
C.
featuresTopic
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
-
D.
featuresFormat
Indicates that something (such as a product, service, or medium) is presented, delivered, or made available in a particular format or configuration.
-
E.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26b1b4881908ae4b1b2c9b268a0 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.