Triple
T3194806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Put It in a Love Song |
E66908
|
entity |
| Predicate | singleStatus |
P127
|
FINISHED |
| Object | not released as an official single |
—
|
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: not released as an official single | Statement: [Put It in a Love Song, singleStatus, not released as an official single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleStatus Context triple: [Put It in a Love Song, singleStatus, not released as an official single]
-
A.
singleBy
Indicates that an entity is not in a romantic relationship and is considered single according to a specified criterion or context.
-
B.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
singleType
Indicates that an entity belongs to exactly one specific type or category, with no additional types assigned.
-
D.
singleFrom
Indicates that one entity is derived as a single, distinct item from another source or collection.
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada714dbcc8190a7ad21b3c957f151 |
completed | March 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.