Triple
T1260389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia's 8th congressional district |
E12484
|
entity |
| Predicate | congressionalNumber |
P26352
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Virginia's 8th congressional district, congressionalNumber, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congressionalNumber Context triple: [Virginia's 8th congressional district, congressionalNumber, 8]
-
A.
legislatureNumber
Indicates the specific numbered session or term of a legislative body associated with an entity or event.
-
B.
legislativeTermNumber
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
-
C.
representedInCongressBy
Indicates that one entity serves as the official congressional representative (e.g., legislator) for another entity (such as a person, group, or geographic area).
-
D.
congressName
Indicates the official name or title assigned to a particular congress or legislative session.
-
E.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc503e88190b237210a61228dd8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd98b62c8190a5f6710345c0537d |
completed | March 1, 2026, 10:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.