Triple
T3200826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Production Act of 1950 |
E67044
|
entity |
| Predicate | amendedFor |
P46107
|
FINISHED |
| Object | Cold War mobilization needs |
—
|
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: Cold War mobilization needs | Statement: [Defense Production Act of 1950, amendedFor, Cold War mobilization needs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amendedFor Context triple: [Defense Production Act of 1950, amendedFor, Cold War mobilization needs]
-
A.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
B.
partiallyAmendedBy
Indicates that an existing item (such as a document, law, or agreement) has been modified in part, but not completely replaced, by another item.
-
C.
amendedAt
Indicates the date and time at which an existing entity or record was modified or updated.
-
D.
hasAmendments
Indicates that one entity (such as a document, law, or agreement) includes or is associated with one or more modifications, changes, or additions made after its original creation.
-
E.
legalAmendment
Indicates a formal change or modification made to an existing law, regulation, or legal document.
- F. None of above. chosen
Provenance (4 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9aedef08190824bdf508f85f06f |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.