Triple
T2830930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Plan |
E62232
|
entity |
| Predicate | upperHouseChosenBy |
P19306
|
FINISHED |
| Object | lower house |
—
|
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: lower house | Statement: [Virginia Plan, upperHouseChosenBy, lower house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperHouseChosenBy Context triple: [Virginia Plan, upperHouseChosenBy, lower house]
-
A.
selectionMethodUpperHouse
chosen
Indicates how members of the upper house are chosen or appointed (e.g., by election, appointment, or other selection procedures).
-
B.
upperHouse
Indicates that one entity functions as the higher or upper legislative chamber in relation to a given political or governmental system.
-
C.
votingSystemUpperHouse
Indicates a relationship where a specified voting system is used to elect or constitute the members of an upper legislative house.
-
D.
upperHouseInvolved
Indicates that the upper legislative chamber (e.g., senate) participates in, influences, or is formally involved in the referenced action, process, or decision.
-
E.
upperHouseCreated
Indicates that an upper legislative chamber (such as a senate) has been formally established or brought into existence.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebd5a2c81908f0e30a0ae0eb8df |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.