Triple
T36691696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murphy–Weygand Agreement |
E905972
|
entity |
| Predicate | assistanceProvider |
P16415
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [Murphy–Weygand Agreement, assistanceProvider, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assistanceProvider Context triple: [Murphy–Weygand Agreement, assistanceProvider, United States]
-
A.
assistanceMayInclude
Indicates that one entity’s assistance to another can optionally encompass or involve a specified type, component, or aspect of help.
-
B.
assistance
Indicates providing help, support, or aid from one entity to another to facilitate a task, goal, or need.
-
C.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
D.
soughtAssistanceFrom
Indicates that one entity actively requested help, support, or guidance from another entity.
-
E.
providesSupportTo
chosen
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7e6b3f481909ad2b44e11f578f2 |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.