Triple

T7509
Position Surface form Disambiguated ID Type / Status
Subject Boston Tea Party E149 entity
Predicate aftermath P374 FINISHED
Object closure of Boston Harbor under the Boston Port Act 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: closure of Boston Harbor under the Boston Port Act | Statement: [Boston Tea Party, aftermath, closure of Boston Harbor under the Boston Port Act]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aftermath
Context triple: [Boston Tea Party, aftermath, closure of Boston Harbor under the Boston Port Act]
  • A. result chosen
    Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
  • B. era
    Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
  • C. backing
    Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
  • D. reconstructedAfter
    Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
  • E. near
    Indicates that one entity is located at a short distance from another entity in space or position.
  • 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_69a23bb612708190b09f25385e4b63d1 completed Feb. 28, 2026, 12:49 a.m.
NER Named-entity recognition batch_69a241a55ac081909e95b71c97db8140 completed Feb. 28, 2026, 1:15 a.m.
PD Predicate disambiguation batch_69a23fe1cf38819080ea56c40bf2632e completed Feb. 28, 2026, 1:07 a.m.
Created at: Feb. 28, 2026, 12:54 a.m.