Triple
T31100367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortals |
E792655
|
entity |
| Predicate | payAndRations |
P171143
|
FINISHED |
| Object | better supplied than regular infantry |
—
|
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: better supplied than regular infantry | Statement: [Immortals, payAndRations, better supplied than regular infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payAndRations Context triple: [Immortals, payAndRations, better supplied than regular infantry]
-
A.
payAndPrivileges
Indicates that one party provides or receives compensation and associated benefits or entitlements from another party.
-
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.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
D.
paysAfter
Indicates that one entity makes a payment to another entity only after a specified event, condition, or time has occurred.
-
E.
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.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6e0b888190a417ae712c42db0d |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:03 p.m.