Triple

T351352
Position Surface form Disambiguated ID Type / Status
Subject Congress of the Confederation E7448 entity
Predicate reasonForReplacement P6009 FINISHED
Object adoption of the United States Constitution 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: adoption of the United States Constitution | Statement: [Congress of the Confederation, reasonForReplacement, adoption of the United States Constitution]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForReplacement
Context triple: [Congress of the Confederation, reasonForReplacement, adoption of the United States Constitution]
  • A. reasonForChange chosen
    Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
  • B. changeReason
    Indicates the reason or justification for a modification or change made to an entity or its state.
  • C. reasonForReoffer
    Indicates the reason or justification for presenting something again after it was previously offered.
  • D. reasonForRelocation
    Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
  • E. reasonForDecline
    Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb7df63c8190b7cd1bcfdfd96187 completed Feb. 28, 2026, 1:19 p.m.
PD Predicate disambiguation batch_69a2e955d1f88190bd687c46fa7c5469 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.