Triple

T15454002
Position Surface form Disambiguated ID Type / Status
Subject Consular Guard E371721 entity
Predicate payAndPrivileges P118850 FINISHED
Object higher pay than line troops 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: higher pay than line troops | Statement: [Consular Guard, payAndPrivileges, higher pay than line troops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: payAndPrivileges
Context triple: [Consular Guard, payAndPrivileges, higher pay than line troops]
  • A. payGrade
    Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
  • B. payReform
    Indicates a relationship where an authority changes or restructures the pay system, such as salaries or compensation terms, for a group of people.
  • C. pays
    Indicates that one entity gives money or another form of compensation to another entity, typically in exchange for goods, services, or to settle a debt.
  • D. payCategory
    Indicates the classification of a payment or compensation into a specific category (such as type, purpose, or pay band) within a payment or payroll context.
  • E. paidBy
    Indicates that a payment or financial obligation is made or settled by the specified entity.
  • 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_69d85cc8bd308190886949510b42e764 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f131b1481909ff099c3b844ee07 completed April 16, 2026, 1:44 a.m.
PD Predicate disambiguation batch_69ded28276f481908c2038bb301e57cf completed April 14, 2026, 11:49 p.m.
PDg Predicate description generation batch_69ded57005608190886cd01f640dfedb completed April 15, 2026, 12:01 a.m.
Created at: April 10, 2026, 3:31 a.m.