Triple

T13899384
Position Surface form Disambiguated ID Type / Status
Subject Queensland public service E334178 entity
Predicate employsOccupation P44925 FINISHED
Object administrative officers 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: administrative officers | Statement: [Queensland public service, employsOccupation, administrative officers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: employsOccupation
Context triple: [Queensland public service, employsOccupation, administrative officers]
  • A. subjectOccupation
    Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
  • B. occupationType
    Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
  • C. employedRole chosen
    Indicates that an entity holds or performs a specific role or position within an employment or work context.
  • D. mainOccupationFrom
    Indicates that the specified occupation is the primary or main job held by the given entity.
  • E. usedByOccupation
    Indicates that something (such as a tool, method, or resource) is utilized in the performance of a particular occupation or job.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de25d8897881908b770cdb565898d4 completed April 14, 2026, 11:32 a.m.
PD Predicate disambiguation batch_69dd464b1ab48190ae50bfc902bf6ef7 completed April 13, 2026, 7:38 p.m.
Created at: April 9, 2026, 10:15 p.m.