Triple

T11631524
Position Surface form Disambiguated ID Type / Status
Subject Real Madrid Castilla E276408 entity
Predicate reserveTeamRules P100669 FINISHED
Object cannot play in same division as Real Madrid CF 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: cannot play in same division as Real Madrid CF | Statement: [Real Madrid Castilla, reserveTeamRules, cannot play in same division as Real Madrid CF]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reserveTeamRules
Context triple: [Real Madrid Castilla, reserveTeamRules, cannot play in same division as Real Madrid CF]
  • A. sanctioningRules
    Indicates the rules or conditions under which sanctions or penalties are imposed in response to certain actions or behaviors.
  • B. rulesBy
    Indicates that one entity governs, controls, or exercises authoritative power over another entity.
  • C. supportRules
    Indicates that one entity provides justification, backing, or validation for the rules or constraints defined by another entity.
  • D. hasRulebook
    Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
  • E. reservationPolicy
    Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a25aa9188190ab13d79139f37e7e completed April 10, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69d85dd94bdc819091fa2ed33eb31624 completed April 10, 2026, 2:18 a.m.
PDg Predicate description generation batch_69d87f2e67108190ac36bf47aac12fa8 completed April 10, 2026, 4:40 a.m.
Created at: April 8, 2026, 9:39 p.m.