Triple
T494463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 80th United States Congress |
E10260
|
entity |
| Predicate | legislativeTermEnd |
P4346
|
FINISHED |
| Object | January 3, 1949 |
—
|
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, 1949 | Statement: [80th United States Congress, legislativeTermEnd, January 3, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeTermEnd Context triple: [80th United States Congress, legislativeTermEnd, January 3, 1949]
-
A.
officeholderEndTime
chosen
Indicates the time or date at which a person’s term in a particular office or position comes to an end.
-
B.
parliamentaryRepresentationEndYear
Indicates the calendar year in which an entity’s parliamentary representation or membership formally ended.
-
C.
vicePresidentialTermEnd
Indicates the date or point in time when an individual's service in a specific vice presidential term comes to an end.
-
D.
legislativeTermNumber
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
-
E.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0fdd5608190815fa36485df8962 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.