Triple

T5579205
Position Surface form Disambiguated ID Type / Status
Subject Stamp Act Congress E146598 entity
Predicate reasonForMeeting P20908 FINISHED
Object opposition to the Stamp Act of 1765 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: opposition to the Stamp Act of 1765 | Statement: [Stamp Act Congress, reasonForMeeting, opposition to the Stamp Act of 1765]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForMeeting
Context triple: [Stamp Act Congress, reasonForMeeting, opposition to the Stamp Act of 1765]
  • A. reasonForEvent chosen
    Indicates that one event occurs as a consequence of, or is motivated or explained by, another specified cause or reason.
  • B. reasonForTime
    Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
  • C. statedReason
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • D. reasonForUse
    Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
  • E. notabilityReason
    Indicates the specific cause, basis, or context for which an entity is considered notable or significant.
  • 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_69c0090287a08190b4098411effe970c completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c0206bfea08190aa2c8df9f88013ac completed March 22, 2026, 5:01 p.m.
PD Predicate disambiguation batch_69c01b147cc081909237f3f2967d4cb8 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:37 p.m.