Triple
T8842206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love in the Dark |
E210413
|
entity |
| Predicate | hasRecordingPeriod |
P44812
|
FINISHED |
| Object | 2014–2015 |
—
|
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: 2014–2015 | Statement: [Love in the Dark, hasRecordingPeriod, 2014–2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingPeriod Context triple: [Love in the Dark, hasRecordingPeriod, 2014–2015]
-
A.
mainRecordingPeriod
chosen
Indicates the primary time span during which the recording activity took place.
-
B.
recordingPeriodRequirement
Indicates the required duration or time period over which records or data must be kept or maintained.
-
C.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
-
D.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
E.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60876c6c8190b1b490e447e1cf4b |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.