Triple
T1146675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland House of Delegates |
E23580
|
entity |
| Predicate | seatsForParty |
P26049
|
FINISHED |
| Object | Democratic Party majority (as of 2024) |
—
|
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: Democratic Party majority (as of 2024) | Statement: [Maryland House of Delegates, seatsForParty, Democratic Party majority (as of 2024)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatsForParty Context triple: [Maryland House of Delegates, seatsForParty, Democratic Party majority (as of 2024)]
-
A.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
hasReservedSeats
Indicates that specific seats have been set aside or allocated in advance for a particular entity or purpose.
-
C.
seatingConfiguration
Indicates how seats are arranged or organized relative to each other in a given context.
-
D.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
E.
numberOfSittings
Indicates the total count of distinct sittings or sessions associated with an entity or event.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:44 p.m.