Triple

T21793900
Position Surface form Disambiguated ID Type / Status
Subject appointments committee E538042 entity
Predicate mayHaveAuthorityLevel P69042 FINISHED
Object advisory only 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: advisory only | Statement: [appointments committee, mayHaveAuthorityLevel, advisory only]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayHaveAuthorityLevel
Context triple: [appointments committee, mayHaveAuthorityLevel, advisory only]
  • A. mayHaveRole
    Indicates that an entity is permitted or eligible to hold or perform a specified role.
  • B. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • C. authorizationLevel chosen
    Indicates the degree or tier of access rights or permissions granted to an entity within a system or context.
  • D. mayGrant
    Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
  • E. authorityGranted
    Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
  • 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_69e0c4733f4081909a86622e7e6d15d2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f06221d1f4819089bb113d808d79c2 completed April 28, 2026, 7:30 a.m.
PD Predicate disambiguation batch_69e6be751ce881909badced245ef76c7 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:52 p.m.