Triple
T720715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agricultural Adjustment Act of 1938 |
E14609
|
entity |
| Predicate | coversCommodity |
P3553
|
FINISHED |
| Object | wheat |
—
|
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: wheat | Statement: [Agricultural Adjustment Act of 1938, coversCommodity, wheat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversCommodity Context triple: [Agricultural Adjustment Act of 1938, coversCommodity, wheat]
-
A.
commodity
chosen
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
B.
alsoCovers
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
C.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
D.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
E.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58fa41c819082de2cc4e0cb2943 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.