Triple
T33608260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States congressional resolutions |
E860917
|
entity |
| Predicate | mayBeNumberedAs |
P37553
|
FINISHED |
| Object | H.Res. |
—
|
NE NERFINISHED |
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: H.Res. | Statement: [United States congressional resolutions, mayBeNumberedAs, H.Res.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeNumberedAs Context triple: [United States congressional resolutions, mayBeNumberedAs, H.Res.]
-
A.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
B.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
C.
mayBeRenumbered
Indicates that an entity’s identifier or numbering is allowed to change under certain conditions.
-
D.
isNumberedWithinState
Indicates that an entity has an assigned number that is unique or valid only within the context or boundaries of a particular state.
-
E.
isNumberedRelativeTo
Indicates that one entity’s numbering or ordinal position is defined or interpreted in relation 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:41 a.m.