Triple
T16010376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratonhnhaké:ton |
E388322
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Connor |
E685858
|
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: Connor | Statement: [Ratonhnhaké:ton, alsoKnownAs, Connor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Connor Context triple: [Ratonhnhaké:ton, alsoKnownAs, Connor]
-
A.
Connor
Connor is a surname most infamously associated with Bull Connor, the segregationist Birmingham, Alabama public safety commissioner whose brutal tactics against civil rights protesters in the 1960s drew national outrage.
-
B.
Connor
chosen
Connor is a masculine given name of Irish origin, commonly used in English-speaking countries.
-
C.
Connor
Connor is a major character from the TV series "Angel," known as the superhuman son of the vampire Angel and central to several of the show's key storylines.
-
D.
Connor
Connor is a historic town in County Antrim, Northern Ireland, traditionally associated with an early Christian bishopric.
-
E.
Conor
Conor is a masculine given name of Irish origin, commonly used in English-speaking countries.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1828f8c688190a6b365f9140cd2d8 |
completed | April 17, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf24a9d8819083d7b11d71442da6 |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 4:55 a.m.