Triple
T3173910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 110th United States Congress |
E66415
|
entity |
| Predicate | metInSecondSession |
P36357
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [110th United States Congress, metInSecondSession, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metInSecondSession Context triple: [110th United States Congress, metInSecondSession, 2008]
-
A.
secondSessionStart
Indicates the point in time when a second or subsequent session begins.
-
B.
hasSecondaryMeeting
Indicates that an entity is associated with an additional, follow-up, or subordinate meeting beyond a primary one.
-
C.
meetsBetweenSessionsOf
Indicates that one entity meets another during the interval between scheduled sessions or events.
-
D.
sessionOf
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
E.
secondSessionStartYear
chosen
Indicates the calendar year in which an entity’s second session begins.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada670c800819098937783e2b05c7a |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.