Triple

T23004373
Position Surface form Disambiguated ID Type / Status
Subject Toledo Strip E572720 entity
Predicate legallyResolvedBy P111559 FINISHED
Object U.S. Congress compromise of 1836 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: U.S. Congress compromise of 1836 | Statement: [Toledo Strip, legallyResolvedBy, U.S. Congress compromise of 1836]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legallyResolvedBy
Context triple: [Toledo Strip, legallyResolvedBy, U.S. Congress compromise of 1836]
  • A. disputeResolvedBy chosen
    Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
  • B. disputeResolvedIn
    Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
  • C. legalConclusion
    Indicates that a situation, set of facts, or argument leads to or supports a specific determination or outcome under the law.
  • D. legalOutcome
    Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
  • E. resolvedIn
    Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
  • 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_69e245b6a3ac81908087599eefe3e365 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f183556cd08190b18780680bc4f23e completed April 29, 2026, 4:04 a.m.
PD Predicate disambiguation batch_69ef3b9cd5488190bcd23183179f48cd completed April 27, 2026, 10:34 a.m.
Created at: April 17, 2026, 3:51 p.m.