Triple
T35520211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlacht bei Hastenbeck |
E1026530
|
entity |
| Predicate | KoordinatenTyp |
P22467
|
FINISHED |
| Object | Schlachtfeld |
—
|
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: Schlachtfeld | Statement: [Schlacht bei Hastenbeck, KoordinatenTyp, Schlachtfeld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KoordinatenTyp Context triple: [Schlacht bei Hastenbeck, KoordinatenTyp, Schlachtfeld]
-
A.
hasCoordinatesType
chosen
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
-
B.
gridReferenceType
Indicates the specific system or format used to express a location’s position within a spatial grid.
-
C.
pointsType
Indicates that one entity is classified as a specific type or category of points associated with another entity.
-
D.
pointType
Indicates the specific category or classification assigned to a point within a given context or system.
-
E.
coordinateReferenceSystemType
Indicates the specific kind or category of coordinate reference system (e.g., geographic, projected, vertical) associated with a spatial dataset or geometry.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.