Triple
T2229120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 83rd United States Congress |
E48722
|
entity |
| Predicate | firstSessionStartYear |
P6892
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [83rd United States Congress, firstSessionStartYear, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSessionStartYear Context triple: [83rd United States Congress, firstSessionStartYear, 1953]
-
A.
firstMeetingYear
Indicates the calendar year in which two entities first met or had their initial encounter.
-
B.
firstYearPlayed
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
-
C.
firstSessionStart
chosen
Indicates the point in time when an entity’s very first session or interaction begins.
-
D.
firstCycleYear
Indicates the year in which the first cycle, phase, or iteration of a recurring process begins.
-
E.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0685b688190857a76c1043f4b92 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.