Triple

T31308209
Position Surface form Disambiguated ID Type / Status
Subject Unconsol. Laws E798390 entity
Predicate hasUserNeed P171646 FINISHED
Object used to locate special or local statutory provisions not found in consolidated laws 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: used to locate special or local statutory provisions not found in consolidated laws | Statement: [Unconsol. Laws, hasUserNeed, used to locate special or local statutory provisions not found in consolidated laws]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUserNeed
Context triple: [Unconsol. Laws, hasUserNeed, used to locate special or local statutory provisions not found in consolidated laws]
  • A. hasUser
    Indicates that an entity is associated with or linked to a specific user.
  • B. meetsNeedOf
    Indicates that one entity sufficiently fulfills or satisfies the requirement, demand, or expectation specified by another entity.
  • C. hasManagementNeed
    Indicates that an entity requires management, oversight, or intervention to address a particular condition, resource, or situation.
  • D. hasAdaptationNeed
    Indicates that an entity requires some form of adaptation or adjustment to better suit specific conditions, contexts, or needs.
  • E. hasUserService
    Indicates that an entity is associated with or utilizes a particular user-related service.
  • 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_69f224e0bd4c8190aab9b29a73f7aa3c completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6a1ac56b88190a820434b65c9fa23 completed May 3, 2026, 1:15 a.m.
PD Predicate disambiguation batch_69f69fe463248190aa78128abeab1183 completed May 3, 2026, 1:07 a.m.
PDg Predicate description generation batch_69f6a0e920cc8190a943fdd0594906c5 completed May 3, 2026, 1:12 a.m.
Created at: April 29, 2026, 9:14 p.m.