Triple

T19811848
Position Surface form Disambiguated ID Type / Status
Subject Royal Indian Navy shore establishments E475966 entity
Predicate providedTrainingIn P96696 FINISHED
Object seamanship 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: seamanship | Statement: [Royal Indian Navy shore establishments, providedTrainingIn, seamanship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: providedTrainingIn
Context triple: [Royal Indian Navy shore establishments, providedTrainingIn, seamanship]
  • A. receivedTrainingIn chosen
    Indicates that one entity has undergone or been provided with training or instruction in a particular field, skill, or subject associated with another entity.
  • B. trainingProvidedAt
    Indicates that a training activity or program is conducted or delivered at a specific location or venue.
  • C. hasTrainingFor
    Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
  • D. providesTrainingFor
    Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
  • E. providesTrainingSetting
    Indicates that one entity serves as the environment or context in which training or educational activities are conducted for another entity.
  • 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_69d8e51bc4208190a1c57d8c5d1b15e4 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6542c9c5c81908772e88caa067e63 completed April 20, 2026, 4:28 p.m.
PD Predicate disambiguation batch_69e5305858108190bbbfdb9ba3ab9f80 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 1:50 p.m.