Triple
T33912231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junebug |
E869346
|
entity |
| Predicate | hasDirectorContext |
P198584
|
FINISHED |
| Object | Spike Lee |
—
|
NE NERFINISHED |
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: Spike Lee | Statement: [Junebug, hasDirectorContext, Spike Lee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectorContext Context triple: [Junebug, hasDirectorContext, Spike Lee]
-
A.
hasDocumentContext
Indicates that a document is associated with, or interpreted within, a specific contextual framework or situation.
-
B.
hasLocalContext
Indicates that something exists or occurs within a specific, surrounding situational or environmental context tied to a particular place or scope.
-
C.
hasPerformanceContext
Indicates that an entity is associated with a specific performance-related situation, setting, or set of conditions under which it operates or is evaluated.
-
D.
hasSeriesContext
Indicates that something is associated with, or occurs within, the broader context of a particular series or sequence.
-
E.
hasOperatorContext
Indicates that an entity is associated with, or occurs within, a specific operator’s execution or operational 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_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69fef3cdea708190af41c1ff23b68f88 |
completed | May 9, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:48 a.m.