Triple
T28018340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopewell (local place name) |
E707613
|
entity |
| Predicate | isNameSourceOf |
P36337
|
FINISHED |
| Object | Hopewell Gap |
—
|
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: Hopewell Gap | Statement: [Hopewell (local place name), isNameSourceOf, Hopewell Gap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNameSourceOf Context triple: [Hopewell (local place name), isNameSourceOf, Hopewell Gap]
-
A.
usedAsNameSourceFor
chosen
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
B.
isMajorSourceOf
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
-
C.
isOfficialSourceFor
Indicates that one entity is recognized as an authoritative or formally sanctioned provider of information or content about another entity.
-
D.
isBestKnownFrom
Indicates that an entity is primarily or most famously recognized in connection with a particular source, context, or work.
-
E.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
- F. None of above.
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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 8:08 p.m.