Triple
T22923503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania's 18th congressional district |
E569227
|
entity |
| Predicate | mapRedrawnIn |
P150277
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Pennsylvania's 18th congressional district, mapRedrawnIn, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapRedrawnIn Context triple: [Pennsylvania's 18th congressional district, mapRedrawnIn, 2002]
-
A.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
-
B.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
C.
mapsFocus
Indicates that one entity serves as the primary subject, area, or aspect of attention, emphasis, or concentration for another entity.
-
D.
mapsAs
Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
-
E.
mapNumber
Indicates a correspondence where each element in one set or collection is assigned a specific numeric value in another set or domain.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d7973c8190b09a5690fd1d3f28 |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:43 p.m.