Triple
T28018339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopewell (local place name) |
E707613
|
entity |
| Predicate | hasRelatedFeature |
P33476
|
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), hasRelatedFeature, Hopewell Gap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedFeature Context triple: [Hopewell (local place name), hasRelatedFeature, Hopewell Gap]
-
A.
belongsToFeature
Indicates that one entity is a component, attribute, or part of a larger feature or functionality associated with another entity.
-
B.
hasRelation
chosen
Indicates that there exists some specified relationship or association between two entities.
-
C.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
D.
hasNeighboringFeature
Indicates that one feature is located adjacent to or directly next to another feature in space.
-
E.
hasRelatedPolygon
Indicates that one entity is associated with another entity that is represented or defined as a polygon.
- 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_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: April 27, 2026, 8:08 p.m.