Triple
T30734636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Sobotka |
E782514
|
entity |
| Predicate | connectedToPlotline |
P146205
|
FINISHED |
| Object | disappearance of women in the shipping container |
—
|
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: disappearance of women in the shipping container | Statement: [Nick Sobotka, connectedToPlotline, disappearance of women in the shipping container]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToPlotline Context triple: [Nick Sobotka, connectedToPlotline, disappearance of women in the shipping container]
-
A.
connectedToPlotElement
chosen
Indicates that one element is linked or related to a specific plot element within a narrative structure.
-
B.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
C.
connectionLine
Indicates a direct link or path that connects two entities within a system or structure.
-
D.
coPlotter
Indicates that two or more entities jointly create, develop, or contribute to the plot of a narrative work.
-
E.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 29, 2026, 8:37 p.m.