Triple
T1064633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Congress |
E22981
|
entity |
| Predicate | holdsHearingOn |
P11604
|
FINISHED |
| Object | securities regulation |
—
|
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: securities regulation | Statement: [U.S. Congress, holdsHearingOn, securities regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsHearingOn Context triple: [U.S. Congress, holdsHearingOn, securities regulation]
-
A.
heldPublicHearings
chosen
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
B.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
-
C.
hearsCasesAgainst
Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
-
D.
trialHeldIn
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
-
E.
paroleHearings
Indicates that one or more formal hearings are held to evaluate an incarcerated individual's eligibility or suitability for parole.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b90f91248190ace1534a51b82bdd |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.