Triple
T31302481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daylight |
E798245
|
entity |
| Predicate | usedToTitleWorksAbout |
P177582
|
FINISHED |
| Object | romantic relationships |
—
|
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: romantic relationships | Statement: [Daylight, usedToTitleWorksAbout, romantic relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToTitleWorksAbout Context triple: [Daylight, usedToTitleWorksAbout, romantic relationships]
-
A.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
B.
usedAsTitleOn
Indicates that something functions as a title applied to or displayed on a particular entity.
-
C.
usedTitleFrom
Indicates that one entity has employed or adopted the title originating from another entity.
-
D.
usedAsTitleOnReleasesBy
Indicates that a work or phrase is used as the title on releases (such as albums, singles, or other published items) created by a specific artist or entity.
-
E.
usedAsWorkingTitleDuring
Indicates that one title temporarily served as the working or provisional title of a work during a specified time period.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 29, 2026, 9:14 p.m.