Triple
T18678401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parchim district |
E456662
|
entity |
| Predicate | hadGeographicalFeature |
P1094
|
FINISHED |
| Object | forests |
—
|
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: forests | Statement: [Parchim district, hadGeographicalFeature, forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadGeographicalFeature Context triple: [Parchim district, hadGeographicalFeature, forests]
-
A.
refersToGeographicFeature
Indicates that one entity makes reference to, denotes, or is associated with a specific geographic feature such as a landform, body of water, or other physical location.
-
B.
hasNaturalFeature
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
-
C.
locatedInGeographicFeature
Indicates that something is situated within or on a specific natural geographic feature (such as a mountain, river, valley, or lake).
-
D.
hasGeographyCharacteristic
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
E.
physicalFeature
Indicates that one entity possesses or exhibits a particular physical characteristic or attribute.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b26cb408190a4e209c0d4ff31ba |
completed | April 19, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.