Triple
T10787992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadley |
E254496
|
entity |
| Predicate | sharesNameWith |
P15168
|
FINISHED |
| Object | Hadley (place name) |
E254496
|
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: Hadley (place name) | Statement: [Hadley, sharesNameWith, Hadley (place name)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hadley (place name) Context triple: [Hadley, sharesNameWith, Hadley (place name)]
-
A.
Hadley Wood
Hadley Wood is a suburban residential area in the London Borough of Enfield, known for its affluent character, green spaces, and golf course.
-
B.
Hadley
chosen
Hadley is a given name most notably borne by Hadley Richardson, the first wife of writer Ernest Hemingway.
-
C.
Hadleyville
Hadleyville is the fictional small Western town in the classic 1952 film "High Noon," where the story’s tense showdown unfolds.
-
D.
Healey
Healey is a surname of Irish origin borne by various notable individuals in politics, sports, and the arts.
-
E.
Healey
Healey is a locality or district that forms part of the town of Whitworth in England.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d65fcc8190ab5573a861409c56 |
completed | April 9, 2026, 5:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de56199d088190938a72105540cf66 |
completed | April 14, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:17 p.m.