Triple

T3859444
Position Surface form Disambiguated ID Type / Status
Subject An Act to Promote the Defense of the United States E90097 entity
Predicate axisOpponentsAssisted P52399 FINISHED
Object Allies fighting Germany 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: Allies fighting Germany | Statement: [An Act to Promote the Defense of the United States, axisOpponentsAssisted, Allies fighting Germany]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: axisOpponentsAssisted
Context triple: [An Act to Promote the Defense of the United States, axisOpponentsAssisted, Allies fighting Germany]
  • A. assistsWith
    Indicates that one entity helps or supports another entity in performing or accomplishing a specific task, activity, or objective.
  • B. opponentStrength
    Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
  • C. keyOpponents
    Indicates that the subject has primary or most significant opponents identified by the object.
  • D. wasAssistedBy
    Indicates that an entity carried out an action or achieved a result with the help or support of another entity.
  • E. consideredOpponentsAs
    Indicates that one entity regarded or treated another entity as an opponent or adversary.
  • 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_69aed95b3c088190a8f85d19e6070599 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec1ff39c8190b83a88abd840a0e3 completed March 9, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69aee752c8a48190a670f73ed0bf1e61 completed March 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69aeeb828fb08190901d51edbe8bd304 completed March 9, 2026, 3:47 p.m.
Created at: March 9, 2026, 3:19 p.m.