Triple

T1076236
Position Surface form Disambiguated ID Type / Status
Subject OLRC E23844 entity
Predicate nonSubstantiveFunction P7974 FINISHED
Object does not make policy choices in codification 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: does not make policy choices in codification | Statement: [OLRC, nonSubstantiveFunction, does not make policy choices in codification]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nonSubstantiveFunction
Context triple: [OLRC, nonSubstantiveFunction, does not make policy choices in codification]
  • A. notFunction
    Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
  • B. nonExclusive
    Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
  • C. nonPartisan
    Indicates that an entity is not affiliated with, influenced by, or acting on behalf of any political party or partisan interest.
  • D. notTypicallyUsedFor chosen
    Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
  • E. secondaryFunction
    Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
  • 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_69a493f1ddf48190a99d54b00e99f8ce completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b940d4848190930e73597afd1fcf completed March 1, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69a4b73ba8208190be7f3cef8c18689b completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.