Triple
T5623644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th United States Congress |
E147667
|
entity |
| Predicate | thirdSessionStart |
P32180
|
FINISHED |
| Object | 1796-12-05 |
—
|
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: 1796-12-05 | Statement: [4th United States Congress, thirdSessionStart, 1796-12-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdSessionStart Context triple: [4th United States Congress, thirdSessionStart, 1796-12-05]
-
A.
thirdSessionStartDate
chosen
Indicates the calendar date on which the third session in a sequence is scheduled to begin.
-
B.
secondSessionStart
Indicates the point in time when a second or subsequent session begins.
-
C.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
-
D.
thirdGenerationStart
Indicates the point in time or event at which the third generation of a lineage, product line, or sequence begins.
-
E.
thirdEpisode
Indicates that one entity is the third episode in sequence within a series or season relative to another entity.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02214b4948190b71a9f59499092f6 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.