Triple
T23178731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvin Hartley |
E579088
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Hartley |
—
|
NE NERFINISHED |
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: [Marvin Hartley, hasSurname, Hartley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hartley Context triple: [Marvin Hartley, hasSurname, 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.
Haseldine
Haseldine is the middle name of William Haseldine Pepys, an English scientist and instrument maker active in the late 18th and early 19th centuries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f6cbe5481909444479b7eac47f7 |
completed | April 29, 2026, 4:56 a.m. |
Created at: April 17, 2026, 4:04 p.m.