Triple
T6208325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Kingston |
E138803
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kingston |
E69047
|
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: Kingston | Statement: [Alex Kingston, familyName, Kingston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kingston Context triple: [Alex Kingston, familyName, Kingston]
-
A.
Kingston
chosen
Kingston is a common English surname of Anglo-Saxon origin, historically associated with various towns named Kingston in England.
-
B.
Kingston
Kingston is a historic city in New York State known for being one of the state’s early capitals and a key cultural and economic center in the Hudson Valley region.
-
C.
Kingston
Kingston is a small city in eastern Tennessee that serves as the county seat of Roane County and lies within the greater Knoxville metropolitan area.
-
D.
Kingston
Kingston is a small unincorporated community and historic mining town located in central Nevada, United States.
-
E.
Kingston
Kingston is a borough in northeastern Pennsylvania, United States, situated along the Susquehanna River near the city of Wilkes-Barre.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062870d5881909b8d4e33ff31a907 |
completed | March 22, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c243e2d82c8190bacc282589d28b78 |
completed | March 24, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:21 p.m.