Triple
T6000042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoover Moratorium |
E133569
|
entity |
| Predicate | affectedAgreement |
P67930
|
FINISHED |
| Object | World War I reparations system |
—
|
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: World War I reparations system | Statement: [Hoover Moratorium, affectedAgreement, World War I reparations system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedAgreement Context triple: [Hoover Moratorium, affectedAgreement, World War I reparations system]
-
A.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
B.
affectedProvision
Indicates that a particular legal provision is impacted, modified, or influenced by another action, decision, or provision.
-
C.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
D.
affectedAgency
Indicates that one entity has an effect on, or causes a change in, the agency or capacity for action of another entity.
-
E.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee5e7bc8190aaa87605fa7b102e |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:05 p.m.