Triple
T15519802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Challis |
E368929
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Challis |
E1124530
|
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: Challis | Statement: [James Challis, hasFamilyName, Challis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Challis Context triple: [James Challis, hasFamilyName, Challis]
-
A.
Challis
chosen
Challis is an English surname borne by various notable individuals across fields such as cinematography, science, and public service.
-
B.
Yates
Yates is a surname of English origin borne by various notable individuals across literature, politics, sports, and other fields.
-
C.
Challister
Challister is a small coastal settlement on the island of Whalsay in the Shetland archipelago of Scotland.
-
D.
Nicholl
Nicholl is a surname of British origin, often considered a variant of the name Nicol or Nicholas.
-
E.
Challock
Challock is a rural village and civil parish in the Ashford district of Kent, England, known for its countryside setting and traditional English character.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e040343d9c8190a7d1f197c108bd9d |
completed | April 16, 2026, 1:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d52cf1c8190b18bff0b925355a3 |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 4:04 a.m.