Triple
T7845008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont at-large congressional district |
E181901
|
entity |
| Predicate | numberOfDistrictsInStateSince1930s |
P1679
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Vermont at-large congressional district, numberOfDistrictsInStateSince1930s, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDistrictsInStateSince1930s Context triple: [Vermont at-large congressional district, numberOfDistrictsInStateSince1930s, 1]
-
A.
numberOfDistricts
chosen
Indicates the total count of districts associated with a given entity or area.
-
B.
openedAsDistrictInDecade
Indicates that an entity was first opened or established as a district during a specified decade.
-
C.
numberOfDistrictsPeak
Indicates the maximum number of districts that an entity reaches or has at its highest point over a given period or context.
-
D.
numberOfSenateDistricts
Indicates the total count of senate districts associated with a given entity or jurisdiction.
-
E.
federalDistrictSince
Indicates that an entity has held the status of a federal district starting from a specified point in 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163d92fc8190a4efcb08d6b3d404 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:48 p.m.