Triple
T3173903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 110th United States Congress |
E66415
|
entity |
| Predicate | congressBeganOn |
P46770
|
FINISHED |
| Object | January 3, 2007 |
—
|
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: January 3, 2007 | Statement: [110th United States Congress, congressBeganOn, January 3, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congressBeganOn Context triple: [110th United States Congress, congressBeganOn, January 3, 2007]
-
A.
firstCongressDate
Indicates the calendar date on which the first congress or formal assembly associated with an entity took place.
-
B.
firstConstitutedIn
Indicates the time or context in which an entity (such as an organization, body, or structure) was originally formed or formally established.
-
C.
originalInaugurationDate
Indicates the date on which an entity (such as an office, institution, or facility) was first formally inaugurated or put into official operation.
-
D.
inaugurationYear
Indicates the calendar year in which an entity was formally inaugurated or officially brought into operation.
-
E.
inaugurationDate
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
- 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_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. |
| PDg | Predicate description generation | batch_69ada20880e481908ecac09d49b1f1c3 |
completed | March 8, 2026, 4:21 p.m. |
Created at: March 8, 2026, 3:06 p.m.