Triple
T9700091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts 14th congressional district |
E234753
|
entity |
| Predicate | isFormerDistrict |
P20255
|
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: [Massachusetts 14th congressional district, isFormerDistrict, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerDistrict Context triple: [Massachusetts 14th congressional district, isFormerDistrict, true]
-
A.
formerDistrict
chosen
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
B.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
C.
hasHadMultipleDistrictsHistorically
Indicates that an entity has been divided into more than one district at different times in its history.
-
D.
formerDistrictNameSharedWith
Indicates that two entities once belonged to districts that had the same name in the past.
-
E.
isFederalDistrictUntil
Indicates that an entity functioned as a federal district up to a specified end date or time.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d6eab0c8190abac1b009d625975 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.