Triple
T3688047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulde |
E78272
|
entity |
| Predicate | crossesAdministrativeRegion |
P13729
|
FINISHED |
| Object | district of Leipzig |
—
|
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: district of Leipzig | Statement: [Mulde, crossesAdministrativeRegion, district of Leipzig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesAdministrativeRegion Context triple: [Mulde, crossesAdministrativeRegion, district of Leipzig]
-
A.
crossesRegion
chosen
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
B.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
E.
containsAdministrativeTerritory
Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c960788190b73ede08658846aa |
completed | March 8, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.