Triple
T38515058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kind Lady |
E922319
|
entity |
| Predicate | hasOriginalWorkReleaseDate |
P22704
|
FINISHED |
| Object | 1951-06-14 |
—
|
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: 1951-06-14 | Statement: [Kind Lady, hasOriginalWorkReleaseDate, 1951-06-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalWorkReleaseDate Context triple: [Kind Lady, hasOriginalWorkReleaseDate, 1951-06-14]
-
A.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
B.
hasOriginalWorkMedium
Indicates that an original creative work is associated with a specific medium or material in which it was first produced.
-
C.
originalRelease
chosen
Indicates the initial publication or first official release event of a work or product.
-
D.
hasOriginalAlbumRelease
Indicates that an album or musical work is associated with its first official release instance or edition.
-
E.
hasOriginalWorkSetting
Indicates that an entity is associated with the setting or context in which the original work or source material takes place.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:32 p.m.