Triple
T33912232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junebug |
E869346
|
entity |
| Predicate | appearsInYearContext |
P195198
|
FINISHED |
| Object | 2000 film |
—
|
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: 2000 film | Statement: [Junebug, appearsInYearContext, 2000 film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInYearContext Context triple: [Junebug, appearsInYearContext, 2000 film]
-
A.
endedInYear
Indicates that an event, state, or relationship concluded in the specified calendar year.
-
B.
featuredInYear
Indicates that something was prominently presented, highlighted, or showcased during a specific calendar year.
-
C.
foundInYear
Indicates the specific calendar year in which something was discovered, created, established, or otherwise found.
-
D.
hasPartInYear
Indicates that something includes or contains a specific part, component, or segment that is associated with a particular year.
-
E.
appearsInContextWith
Indicates that two entities are observed or used together within the same situational, textual, or usage context.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: May 1, 2026, 1:48 a.m.