Triple

T30963712
Position Surface form Disambiguated ID Type / Status
Subject nursing sisters of the Canadian Army Medical Corps E788893 entity
Predicate hadRankStatus P34755 FINISHED
Object officer-equivalent status 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: officer-equivalent status | Statement: [nursing sisters of the Canadian Army Medical Corps, hadRankStatus, officer-equivalent status]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadRankStatus
Context triple: [nursing sisters of the Canadian Army Medical Corps, hadRankStatus, officer-equivalent status]
  • A. hadRankSystem
    Indicates that an entity used or was governed by a particular ranking or rank classification system.
  • B. rankStatus chosen
    Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
  • C. hadOfficialStatus
    Indicates that an entity possessed a formally recognized or legally sanctioned status within an official system or authority.
  • D. hasRankCategory
    Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
  • E. hasRanks
    Indicates that one entity possesses, is assigned, or is associated with one or more rank levels or hierarchical positions.
  • 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_69f224c3a6b48190951add9b7b7f0271 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6953bafb88190a860e9c68a3dd4b2 completed May 3, 2026, 12:22 a.m.
PD Predicate disambiguation batch_69f690ef92308190903a54fc74233269 completed May 3, 2026, 12:03 a.m.
Created at: April 29, 2026, 8:54 p.m.