Triple
T15881432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23rd United States Congress |
E385082
|
entity |
| Predicate | firstSessionStartTime |
P120892
|
FINISHED |
| Object | December 2, 1833 |
—
|
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: December 2, 1833 | Statement: [23rd United States Congress, firstSessionStartTime, December 2, 1833]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSessionStartTime Context triple: [23rd United States Congress, firstSessionStartTime, December 2, 1833]
-
A.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
-
B.
firstInvocationDate
Indicates the date on which the entity was first invoked, used, or called for the first time.
-
C.
firstSessionHeldIn
Indicates that the initial or inaugural session of an event, activity, or process took place in a specified location or context.
-
D.
metInFirstSession
Indicates that the entities first met or were introduced to each other during the initial session of an event, program, or interaction.
-
E.
firstTakenAt
Indicates the time or date at which something was initially taken, captured, or recorded for the first time.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.