Triple
T159218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland General Assembly |
E3243
|
entity |
| Predicate | regularSessionBegins |
P1309
|
FINISHED |
| Object | second Wednesday in January |
—
|
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: second Wednesday in January | Statement: [Maryland General Assembly, regularSessionBegins, second Wednesday in January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSessionBegins Context triple: [Maryland General Assembly, regularSessionBegins, second Wednesday in January]
-
A.
convenesRegularSession
chosen
Indicates that an entity formally brings together a group or body for its routine or scheduled meeting.
-
B.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
C.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
D.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
E.
hasAfterHoursSession
Indicates that an entity conducts or participates in a session that takes place outside of regular or standard operating hours.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.