Triple
T7845022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont at-large congressional district |
E181901
|
entity |
| Predicate | hasSingleRepresentativeForState |
P79322
|
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: [Vermont at-large congressional district, hasSingleRepresentativeForState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleRepresentativeForState Context triple: [Vermont at-large congressional district, hasSingleRepresentativeForState, true]
-
A.
representativeOfState
Indicates that an entity serves as an official representative or agent acting on behalf of a particular state or government.
-
B.
numberOfStatesRepresented
Indicates how many distinct states are represented or covered in a given context or entity.
-
C.
provinceRepresented
Indicates that an entity (such as a person or office) serves as the official representative of a particular province.
-
D.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
-
E.
servesStateOrDistrict
Indicates that an entity holds a role or position in service to a specific state or electoral 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_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. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:48 p.m.