Triple

T2996170
Position Surface form Disambiguated ID Type / Status
Subject Snowdrops E81071 entity
Predicate refersToFunction P4342 FINISHED
Object law enforcement within Royal Air Force 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: law enforcement within Royal Air Force | Statement: [Snowdrops, refersToFunction, law enforcement within Royal Air Force]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: refersToFunction
Context triple: [Snowdrops, refersToFunction, law enforcement within Royal Air Force]
  • A. usesFunction
    Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
  • B. refersToPosition
    Indicates that one entity makes reference to, or is associated with, a specific position or location of another entity.
  • C. associatedFunction
    Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
  • D. possibleFunction
    Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
  • E. refersToRole chosen
    Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
  • 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_69ad8b187fc8819085914d3c9ea3142d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99f481688190ae8cd1e057f9dfc7 completed March 8, 2026, 3:47 p.m.
PD Predicate disambiguation batch_69ad9615fefc8190ad96da92519cb7a3 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:59 p.m.