Triple
T17126816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse Hartley |
E415617
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hartley |
E131240
|
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: Hartley | Statement: [Jesse Hartley, familyName, Hartley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hartley Context triple: [Jesse Hartley, familyName, Hartley]
-
A.
Hartley
Hartley is a small census-designated community located in Solano County, California.
-
B.
Hartley
chosen
Hartley is an English-language surname of Old English origin, commonly associated with various notable figures across fields such as science, politics, and the arts.
-
C.
Hartley
Hartley is a village in north-west Kent, England, known for its rural character and residential communities within commuting distance of London.
-
D.
Murston
Murston is a locality within the Swale district of Kent, England, historically associated with brickmaking and now largely a residential suburb.
-
E.
Ainslie
Ainslie is a residential suburb in Canberra, Australia, known for its leafy streets, heritage homes, and proximity to bushland and central city amenities.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f027a3d081908fc1134b50db3d45 |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a013a145e7481909242aab69baeb7a0 |
completed | May 11, 2026, 2:08 a.m. |
Created at: April 10, 2026, 5:36 a.m.