Triple
T670962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House simple resolution |
E12968
|
entity |
| Predicate | numbering |
P3378
|
FINISHED |
| Object | sequential within each Congress |
—
|
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: sequential within each Congress | Statement: [House simple resolution, numbering, sequential within each Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numbering Context triple: [House simple resolution, numbering, sequential within each Congress]
-
A.
numberingType
chosen
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
B.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
C.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
D.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
-
E.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.