Triple

T174012
Position Surface form Disambiguated ID Type / Status
Subject Supreme Court of Guam E3538 entity
Predicate appealRoute P1031 FINISHED
Object certiorari to the Supreme Court of the United States 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: certiorari to the Supreme Court of the United States | Statement: [Supreme Court of Guam, appealRoute, certiorari to the Supreme Court of the United States]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appealRoute
Context triple: [Supreme Court of Guam, appealRoute, certiorari to the Supreme Court of the United States]
  • A. appealsFrom chosen
    Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
  • B. routeNumber
    Indicates the specific identifying number assigned to a route within a transportation or delivery network.
  • C. followsRouteOf
    Indicates that one entity travels along the same path or route that another entity takes or has taken.
  • D. judicialCircuit
    Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
  • E. wasOverturnedByCourt
    Indicates that a prior decision, ruling, or judgment was reversed or nullified by a court.
  • 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_69a25374990081909766d30c79a18e0e completed Feb. 28, 2026, 2:31 a.m.
NER Named-entity recognition batch_69a258e32da88190ad9485aecd0bf08f completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a256689f908190afeb5ee82022a911 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:39 a.m.