Triple

T36014981
Position Surface form Disambiguated ID Type / Status
Subject State Lands Division E1041811 entity
Predicate employees P36133 FINISHED
Object state government employees of Alabama 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: state government employees of Alabama | Statement: [State Lands Division, employees, state government employees of Alabama]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: employees
Context triple: [State Lands Division, employees, state government employees of Alabama]
  • A. employedPeople
    Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
  • B. employeeRight
    Indicates that an employee holds a specific right, entitlement, or privilege within an employment or workplace context.
  • C. hasEmployees chosen
    Indicates that one entity employs one or more other entities as its workers or staff.
  • D. personnel
    Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
  • E. employment
    Indicates a relationship where one entity hires, contracts, or otherwise engages another to perform work or services, typically in exchange for compensation.
  • 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_69f76e2b981881908e4e160607fa82eb completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:07 p.m.