Triple
T131235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 86th United States Congress |
E2657
|
entity |
| Predicate | convenedOn |
P6885
|
FINISHED |
| Object | 1959-01-07 |
—
|
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: 1959-01-07 | Statement: [86th United States Congress, convenedOn, 1959-01-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenedOn Context triple: [86th United States Congress, convenedOn, 1959-01-07]
-
A.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
B.
convenes
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
-
C.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
D.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
E.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2564edb488190974dc00eb9ac37d9 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2585408c881908a25b5c61f300154 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.