Triple

T27148541
Position Surface form Disambiguated ID Type / Status
Subject Texas Government Code provisions on historic preservation E682318 entity
Predicate assignTo P108451 FINISHED
Object Texas Historical Commission NE NERFINISHED

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: Texas Historical Commission | Statement: [Texas Government Code provisions on historic preservation, assignTo, Texas Historical Commission]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: assignTo
Context triple: [Texas Government Code provisions on historic preservation, assignTo, Texas Historical Commission]
  • A. assignedAs
    Indicates that one entity is designated or appointed to perform a specific role, task, or function in relation to another entity.
  • B. allottedTo chosen
    Indicates that something has been assigned or allocated to a particular entity as its designated recipient or user.
  • C. assignsRoleTo
    Indicates that one entity designates or grants a specific role or position to another entity.
  • D. assignedTo
    Indicates that responsibility for a task, item, or role has been designated to a specific entity.
  • E. assignedUnder
    Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
  • 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_69eefaceb2a08190b9659b7f730629f5 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f624c7ad888190b57bb987a8202789 completed May 2, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69f61b40f02081909bd9c3ea73249163 completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 9:12 a.m.