Triple
T531594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mansabdari system |
E12233
|
entity |
| Predicate | salaryBasis |
P2448
|
FINISHED |
| Object | cash payments |
—
|
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: cash payments | Statement: [mansabdari system, salaryBasis, cash payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salaryBasis Context triple: [mansabdari system, salaryBasis, cash payments]
-
A.
salaryType
chosen
Indicates the classification or structure of compensation associated with an entity, such as whether pay is salaried, hourly, commission-based, or another type.
-
B.
salary
Indicates the amount of monetary compensation an entity receives, typically on a regular basis, for work or services performed.
-
C.
payGrade
Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
-
D.
recruitmentBasis
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
E.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.