Triple
T3475105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarke |
E73353
|
entity |
| Predicate | relatedSurname |
P13741
|
FINISHED |
| Object | Clerke |
E73353
|
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: Clerke | Statement: [Clarke, relatedSurname, Clerke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clerke Context triple: [Clarke, relatedSurname, Clerke]
-
A.
Clarke
chosen
Clarke is a common English and Irish surname historically associated with the occupation of a clerk or scholar.
-
B.
Everard
Everard is a masculine given name of Old English origin, historically meaning “brave boar” or “strong as a wild boar.”
-
C.
Humphreys
Humphreys is a small unincorporated community located within Lea County in southeastern New Mexico.
-
D.
Michell
Michell is a given name and surname that functions as a variant spelling of Mitchell.
-
E.
Clive
Clive is a surname most famously associated with Robert Clive, the 18th-century British officer who played a key role in establishing British rule in India.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb593a388190b7786190deba96ed |
completed | March 8, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b373b2058081908558bdea4043b051 |
completed | March 13, 2026, 2:17 a.m. |
Created at: March 8, 2026, 3:17 p.m.