Triple
T22858335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Representatives of the United States |
E566842
|
entity |
| Predicate | firstCongressStartYear |
P46770
|
FINISHED |
| Object | 1789 |
—
|
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: 1789 | Statement: [House of Representatives of the United States, firstCongressStartYear, 1789]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCongressStartYear Context triple: [House of Representatives of the United States, firstCongressStartYear, 1789]
-
A.
firstCongressDate
Indicates the calendar date on which the first congress or formal assembly associated with an entity took place.
-
B.
congressBeganOn
chosen
Indicates the calendar date on which a particular session or term of a congress officially started.
-
C.
firstNationalConventionYear
Indicates the year in which an entity held its first national convention.
-
D.
firstMPStartYear
Indicates the year in which an individual first began serving as a Member of Parliament.
-
E.
firstConstitutedIn
Indicates the time or context in which an entity (such as an organization, body, or structure) was originally formed or formally established.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebe3f9c8190a864f4e84dc7795d |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.