Triple
T32480680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylonian administration |
E830097
|
entity |
| Predicate | taxationBasis |
P59668
|
FINISHED |
| Object | land holdings |
—
|
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: land holdings | Statement: [Babylonian administration, taxationBasis, land holdings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxationBasis Context triple: [Babylonian administration, taxationBasis, land holdings]
-
A.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
B.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
D.
taxRegime
Indicates the system or structure of taxation that governs how taxes are assessed, collected, and applied within a particular context or jurisdiction.
-
E.
hasPropertyTaxBase
chosen
Indicates that one entity serves as the property tax base or source from which another entity’s property tax is assessed or calculated.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c395640c81908808b2d4d40f26e7 |
completed | May 3, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:58 a.m.