Triple

T15006297
Position Surface form Disambiguated ID Type / Status
Subject Takeovers Panel E377719 entity
Predicate establishedToReplace P81350 FINISHED
Object primary role of courts in takeover disputes 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: primary role of courts in takeover disputes | Statement: [Takeovers Panel, establishedToReplace, primary role of courts in takeover disputes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: establishedToReplace
Context triple: [Takeovers Panel, establishedToReplace, primary role of courts in takeover disputes]
  • A. createdToReplace chosen
    Indicates that one entity was intentionally created for the purpose of taking over the role, function, or position of another entity.
  • B. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • C. seeksToReplace
    Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
  • D. establishedTo
    Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
  • E. replacedBecause
    Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7322b5c81909089cbbf816e1436 completed April 15, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69de9a6531a88190acde65199a477350 completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:54 a.m.