Triple
T36558058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himling |
E901746
|
entity |
| Predicate | cartographicName |
P186518
|
FINISHED |
| Object | Himling |
—
|
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: Himling | Statement: [Himling, cartographicName, Himling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicName Context triple: [Himling, cartographicName, Himling]
-
A.
cartographicAuthority
Indicates that an entity has official responsibility for creating, maintaining, or validating cartographic or map-related information for another entity or area.
-
B.
cartographicNote
Indicates a note that provides additional cartographic information or commentary about a map or spatial representation.
-
C.
cartographicContent
Indicates that the resource contains or is associated with map-related or cartographic information.
-
D.
cartographicNotation
Indicates the specific symbols, labels, or graphical conventions used to represent geographic features or spatial information on a map.
-
E.
cartographicType
Indicates the specific kind or category of cartographic representation associated with an entity (e.g., map type or mapping style).
- F. None of above. chosen
Provenance (4 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:11 p.m.