Triple
T2737106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holcombe Hill |
E60655
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Holcombe |
E283911
|
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: Holcombe | Statement: [Holcombe Hill, locatedNear, Holcombe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holcombe Context triple: [Holcombe Hill, locatedNear, Holcombe]
-
A.
Holcombe
chosen
Holcombe is a village in Greater Manchester, England, known for its rural setting and proximity to the prominent Peel Monument on Holcombe Hill.
-
B.
Mauldin
Mauldin is a city in South Carolina, United States, known as a suburban community within the Greenville metropolitan area.
-
C.
Mount Pleasant
Mount Pleasant is a suburban town in Westchester County, New York, known for its residential communities and proximity to major reservoirs and parklands.
-
D.
Mount Pleasant
Mount Pleasant is a prominent sandstone bluff and scenic overlook in Lancaster, Ohio, known for its hiking trails and panoramic views of the surrounding area.
-
E.
Mount Pleasant
Mount Pleasant is a historic, culturally diverse residential neighborhood in Washington, D.C., known for its tree-lined streets, early 20th-century row houses, and vibrant local commerce.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb12e03c8190b270c814ce47b626 |
completed | March 7, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb6a5dda0819092508b9e10030d09 |
completed | March 10, 2026, 6:13 a.m. |
Created at: March 6, 2026, 9:56 p.m.