Triple

T2059433
Position Surface form Disambiguated ID Type / Status
Subject FE Civil E45752 entity
Predicate referencePolicy P35519 FINISHED
Object only NCEES-supplied electronic reference handbook allowed 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: only NCEES-supplied electronic reference handbook allowed | Statement: [FE Civil, referencePolicy, only NCEES-supplied electronic reference handbook allowed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: referencePolicy
Context triple: [FE Civil, referencePolicy, only NCEES-supplied electronic reference handbook allowed]
  • A. reflectsPolicy
    Indicates that one entity embodies, represents, or is aligned with the rules, principles, or stance defined by a particular policy.
  • B. collectionPolicy
    Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
  • C. policySource
    Indicates the origin or authority from which a given policy is derived or issued.
  • D. decisionPublicationPolicy
    Indicates the policy or rules governing how decisions are made public or communicated.
  • E. keyPolicy
    Indicates that a specified policy governs the creation, use, management, or access control of a particular key.
  • 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_69a8891a19508190a12ef1e192308dcb completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb9af42988190a4e977154dd10312 completed March 7, 2026, 5:37 a.m.
PD Predicate disambiguation batch_69abb7ad5a7c8190b92575d6053b3fb7 completed March 7, 2026, 5:29 a.m.
PDg Predicate description generation batch_69abb92f90a881909a1f10b060132a9e completed March 7, 2026, 5:35 a.m.
Created at: March 4, 2026, 7:40 p.m.