Triple
T7222201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electoral Commission Act |
E150285
|
entity |
| Predicate | commissionComposition |
P33619
|
FINISHED |
| Object | 5 U.S. Representatives |
—
|
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: 5 U.S. Representatives | Statement: [Electoral Commission Act, commissionComposition, 5 U.S. Representatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionComposition Context triple: [Electoral Commission Act, commissionComposition, 5 U.S. Representatives]
-
A.
commissionType
Indicates the specific kind or category of commission arrangement that applies to a given transaction or relationship.
-
B.
commissionCommonName
Indicates that an entity is commonly known or referred to by a particular commission-related name.
-
C.
compositionForm
Indicates the structural or organizational form in which something is composed or arranged.
-
D.
compositionDetail
chosen
Indicates that one entity specifies or describes the internal makeup, structure, or constituent elements of another entity.
-
E.
composedIn
Indicates that a creative work was written or musically composed within a particular place or during a specific time period.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b42c5c81908c405f161c35ffb4 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.