Triple
T4358566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 61st United States Congress |
E98609
|
entity |
| Predicate | legislativeSessionsPerTerm |
P11319
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [61st United States Congress, legislativeSessionsPerTerm, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeSessionsPerTerm Context triple: [61st United States Congress, legislativeSessionsPerTerm, 2]
-
A.
hasLegislativeSessionCount
chosen
Indicates the number of legislative sessions associated with a given legislative body, term, or jurisdiction.
-
B.
legislativeTermNumber
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
-
C.
legislativePeriodicity
Indicates how frequently a legislative body or process recurs or is scheduled to occur over time.
-
D.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
E.
legislativeSession
Indicates that an entity is a formal meeting period of a legislative body during which it conducts its official business, such as debating and passing laws.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c7fa1881908bdc844a7142eb65 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.