Triple

T37551086
Position Surface form Disambiguated ID Type / Status
Subject Trial of the Crusader E933590 entity
Predicate hasSharedLockoutWith P190728 FINISHED
Object Trial of the Grand Crusader NE NERFINISHED

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: Trial of the Grand Crusader | Statement: [Trial of the Crusader, hasSharedLockoutWith, Trial of the Grand Crusader]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSharedLockoutWith
Context triple: [Trial of the Crusader, hasSharedLockoutWith, Trial of the Grand Crusader]
  • A. supportsLockoutType
    Indicates that one entity is compatible with or able to operate using a specified lockout type.
  • B. usesLockoutChip
    Indicates that an entity employs a lockout chip mechanism to control or restrict access, operation, or compatibility.
  • C. hadRoleLock
    Indicates that an entity’s role was restricted or fixed, preventing changes to that role during a certain period or context.
  • D. hasShareRestriction
    Indicates that there is a limitation or condition placed on the transfer, sale, or use of shares associated with an entity.
  • E. hasLocksAt
    Indicates that one entity possesses or provides locks that are located at or associated with a specific place or position of another entity.
  • 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_69f76eca55bc8190acf25741793d5dac completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcce2cf9188190b3f65b362203a6a3 completed May 7, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69fcccee6240819084680887731ff64b completed May 7, 2026, 5:33 p.m.
PDg Predicate description generation batch_69fccdd2d84481909a7ce22407def9c7 completed May 7, 2026, 5:37 p.m.
Created at: May 3, 2026, 4:17 p.m.