Triple
T15766180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland's 6th congressional district |
E382225
|
entity |
| Predicate | oneOfOriginalDistricts |
P120248
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Maryland's 6th congressional district, oneOfOriginalDistricts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfOriginalDistricts Context triple: [Maryland's 6th congressional district, oneOfOriginalDistricts, true]
-
A.
formerDistrict
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
B.
geographicallySeparatedDistrictOf
Indicates that one district is a non-contiguous, physically separate part of another district or administrative area.
-
C.
isSingleDistrictFor
Indicates that one district uniquely and exclusively serves or applies to a given entity, with no other districts sharing that role.
-
D.
sourceDistrict
Indicates the district from which something originates, is sent, or is sourced.
-
E.
modernDistrict
Indicates that one administrative district is the contemporary or current counterpart of another, typically older or historical, district.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b8154881908afe5191e6424f15 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.