Triple
T32066337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It's Tough to be a Bug! |
E818891
|
entity |
| Predicate | filmReleaseRelation |
P173507
|
FINISHED |
| Object | opened before the release of A Bug's Life |
—
|
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: opened before the release of A Bug's Life | Statement: [It's Tough to be a Bug!, filmReleaseRelation, opened before the release of A Bug's Life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmReleaseRelation Context triple: [It's Tough to be a Bug!, filmReleaseRelation, opened before the release of A Bug's Life]
-
A.
filmRelease
Indicates the event or relationship in which a film is made publicly available, typically specifying when, where, or how it is released.
-
B.
filmReleaseDate
Indicates the calendar date on which a film was first officially released or made publicly available.
-
C.
filmReleasedOn
Indicates that a film was released on a specific date.
-
D.
filmRecordingReleaseYear
Indicates the calendar year in which a particular film recording was first released to the public.
-
E.
filmReleaseYear
Indicates the calendar year in which a film was first officially 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:22 a.m.