Triple
T17611064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegfried Map |
E428965
|
entity |
| Predicate | cartographicTheme |
P108783
|
FINISHED |
| Object | topography |
—
|
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: topography | Statement: [Siegfried Map, cartographicTheme, topography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicTheme Context triple: [Siegfried Map, cartographicTheme, topography]
-
A.
mapTheme
chosen
Indicates a thematic relationship where a map is associated with, organized by, or visually represents a particular theme or subject.
-
B.
cartographicWork
Indicates a relationship where one entity is a cartographic work (such as a map or chart) that represents geographic information about another entity.
-
C.
cartographyBy
Indicates that one entity is the creator or producer of the cartographic work (such as a map or chart) associated with another entity.
-
D.
cartographicFormat
Indicates the specific cartographic representation or format in which spatial or map-related information is expressed.
-
E.
cartographicSignificance
Indicates the importance or relevance of something within the context of mapping or geographic representation.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2d294881908380b2ab0b4d2503 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.