Triple

T25092583
Position Surface form Disambiguated ID Type / Status
Subject Foss v Harbottle E628501 entity
Predicate isKeyCaseFor P158773 FINISHED
Object shareholder remedies 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: shareholder remedies | Statement: [Foss v Harbottle, isKeyCaseFor, shareholder remedies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyCaseFor
Context triple: [Foss v Harbottle, isKeyCaseFor, shareholder remedies]
  • A. hasCaseInflection
    Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
  • B. isKeyCharacterIn
    Indicates that an entity plays a central or primary role as a main or significant character within another entity, such as a story, game, or narrative work.
  • C. letterCase
    Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
  • D. isCaseSensitiveInStandard
    Indicates that the interpretation or comparison of the entity follows a standard in which letter case differences are treated as significant.
  • E. isStandardKey
    Indicates that a given key conforms to a defined standard or canonical set of keys within a system or context.
  • F. None of above. chosen

Provenance (4 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_69e2ff2f58e881908340527bc5d34f07 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f48b9b687881908fd87a2f5fa0b1e7 completed May 1, 2026, 11:16 a.m.
PD Predicate disambiguation batch_69f48060597c8190a4414e4e4fcb1fec completed May 1, 2026, 10:28 a.m.
PDg Predicate description generation batch_69f48b9058d081908ec9af261ee092e2 completed May 1, 2026, 11:16 a.m.
Created at: April 18, 2026, 6:24 a.m.