Triple
T33039989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keiko |
E845432
|
entity |
| Predicate | filmReleaseAssociated |
P140972
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Keiko, filmReleaseAssociated, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmReleaseAssociated Context triple: [Keiko, filmReleaseAssociated, 1993]
-
A.
filmReleaseRelation
Indicates the relationship between a film and the details of its release, such as date, location, or distribution context.
-
B.
filmAssociatedWith
Indicates a general relationship or connection between a film and another entity, such as a person, organization, event, or work.
-
C.
filmRelease
Indicates the event or relationship in which a film is made publicly available, typically specifying when, where, or how it is released.
-
D.
associatedWithReleaseDateOfFilm
chosen
Indicates a relationship where something is connected to or corresponds with the release date of a film.
-
E.
theatricalReleaseWith
Indicates that two or more entities share the same theatrical release context, such as being released together or as part of the same theatrical event or distribution.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.