Triple
T12489421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connolly |
E298522
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Connelly |
E298522
|
NE 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: Connelly | Statement: [Connolly, hasVariant, Connelly]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Connelly Context triple: [Connolly, hasVariant, Connelly]
-
A.
Connelly
Connelly is a surname most prominently associated with American actress Jennifer Connelly, known for her acclaimed film roles since the 1980s.
-
B.
Conneely
Conneely is an Irish surname, often considered a variant of Connelly, with roots in Gaelic family names.
-
C.
Corrigan
Corrigan is an Irish-origin surname borne by numerous notable figures in fields such as religion, politics, sports, and entertainment.
-
D.
Connel
Connel is a small village in Argyll and Bute on the west coast of Scotland, situated near Oban and known for the Connel Bridge over the narrows of Loch Etive.
-
E.
Connolly
chosen
Connolly is a surname of Irish origin borne by numerous notable figures in politics, arts, and sports.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94de1db9481909ddf70eb81cdb714 |
completed | April 10, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64ba9e1108190b74984d9da9baebe |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:56 p.m.