Triple
T24733572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act in Conditional Restraint of Annates |
E618352
|
entity |
| Predicate | typeOfPaymentAffected |
P158716
|
FINISHED |
| Object | first fruits |
—
|
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: first fruits | Statement: [Act in Conditional Restraint of Annates, typeOfPaymentAffected, first fruits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPaymentAffected Context triple: [Act in Conditional Restraint of Annates, typeOfPaymentAffected, first fruits]
-
A.
payType
Indicates the method or category of payment used in a transaction or compensation arrangement.
-
B.
paymentNetworkType
Indicates the type or category of payment network through which a payment is processed or routed.
-
C.
paymentMethod
Indicates the means or instrument through which a payment is made in a transaction.
-
D.
paymentChangePattern
Indicates a characteristic way in which payment amounts, timing, or methods vary or evolve over a period or across transactions.
-
E.
payerType
Indicates the type or category of entity responsible for making a payment in the relationship.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 4:03 a.m.