Triple
T6500506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Story |
E148870
|
entity |
| Predicate | reRecordedVersionReleaseDate |
P71230
|
FINISHED |
| Object | 2021-02-12 |
—
|
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: 2021-02-12 | Statement: [Love Story, reRecordedVersionReleaseDate, 2021-02-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reRecordedVersionReleaseDate Context triple: [Love Story, reRecordedVersionReleaseDate, 2021-02-12]
-
A.
recordedVersion
Indicates that one entity is a specific recorded version or recording of another entity (such as a work, performance, or composition).
-
B.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
C.
betaReleaseDate
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
-
D.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
E.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:42 p.m.