Triple
T28275005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toni Simmons |
E712962
|
entity |
| Predicate | hasConnectionInPlotWith |
P43975
|
FINISHED |
| Object | Dr. Julian Winston |
—
|
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: Dr. Julian Winston | Statement: [Toni Simmons, hasConnectionInPlotWith, Dr. Julian Winston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionInPlotWith Context triple: [Toni Simmons, hasConnectionInPlotWith, Dr. Julian Winston]
-
A.
hasNotableConnectionTo
chosen
Indicates a significant or noteworthy relationship, association, or link exists between two entities.
-
B.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
E.
isKeyToPlotOf
Indicates that something plays a crucial, defining role in driving or enabling the main events or structure of a plot.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: April 27, 2026, 11:19 p.m.