Triple

T12621368
Position Surface form Disambiguated ID Type / Status
Subject Treaty of St. Louis (1818) E301385 entity
Predicate signing parties role P21253 FINISHED
Object United States represented by federal officials 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: United States represented by federal officials | Statement: [Treaty of St. Louis (1818), signing parties role, United States represented by federal officials]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: signing parties role
Context triple: [Treaty of St. Louis (1818), signing parties role, United States represented by federal officials]
  • A. signerParty
    Indicates the party that formally signs or executes a document, agreement, or instrument.
  • B. signatureRole chosen
    Indicates the specific function or capacity in which an entity participates in a signing or signature-related action.
  • C. signingProcedure
    Indicates the formal process or method by which an agreement, document, or contract is signed or executed between parties.
  • D. signatoryAuthority
    Indicates that an entity has the legal power or authorization to sign documents or agreements on behalf of another party.
  • E. signatoryType
    Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
  • 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_69d7bdeaf49c8190b13800111fa77ea3 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9617b07ec8190b714f04ae6654060 completed April 10, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69d960b195108190ac25bd95e644ace4 completed April 10, 2026, 8:42 p.m.
Created at: April 9, 2026, 5:14 p.m.