Triple
T1017152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cemetery Hill |
E21955
|
entity |
| Predicate | geographicalType |
P17163
|
FINISHED |
| Object | prominent rise of ground |
—
|
LITERAL 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: prominent rise of ground | Statement: [Cemetery Hill, geographicalType, prominent rise of ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalType Context triple: [Cemetery Hill, geographicalType, prominent rise of ground]
-
A.
typeOfToponym
chosen
Indicates the specific category or kind of place name (toponym) that applies to a given geographic entity.
-
B.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
C.
hasGeographyCharacteristic
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
D.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
E.
politicalFeature
Indicates that an entity possesses a political characteristic, attribute, or aspect relevant to governance, power structures, or public policy.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c4d488819081d8214ba0a22fe5 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.