Triple

T291313
Position Surface form Disambiguated ID Type / Status
Subject 12th Man E5999 entity
Predicate legalDisputesInvolved P4511 FINISHED
Object Seattle Seahawks use of the term "12th Man" 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: Seattle Seahawks use of the term "12th Man" | Statement: [12th Man, legalDisputesInvolved, Seattle Seahawks use of the term "12th Man"]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalDisputesInvolved
Context triple: [12th Man, legalDisputesInvolved, Seattle Seahawks use of the term "12th Man"]
  • A. legalCase
    Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
  • B. hasLegalProceeding
    Indicates that there is a formal legal action, case, or proceeding involving the related entities.
  • C. hasLegalIssue chosen
    Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
  • D. legalOutcome
    Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
  • E. legalProcedureUsed
    Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
  • 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_69a25946a7ac8190a78871c210213272 completed Feb. 28, 2026, 2:56 a.m.
NER Named-entity recognition batch_69a25e4f78bc81909a64fd6aaec3b504 completed Feb. 28, 2026, 3:17 a.m.
PD Predicate disambiguation batch_69a25b7d089081909810442c3d0182f6 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 3:02 a.m.