Triple
T15515076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. nationals |
E368813
|
entity |
| Predicate | areSubjectToChangeBy |
P1313
|
FINISHED |
| Object | acts of 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: acts of Congress | Statement: [U.S. nationals, areSubjectToChangeBy, acts of Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areSubjectToChangeBy Context triple: [U.S. nationals, areSubjectToChangeBy, acts of Congress]
-
A.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
B.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
C.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
D.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
E.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04031e62c8190953b61207142af15 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:02 a.m.