Triple
T28893847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Assyrian trade network |
E732784
|
entity |
| Predicate | taxationForm |
P3166
|
FINISHED |
| Object | tolls on caravans |
—
|
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: tolls on caravans | Statement: [Old Assyrian trade network, taxationForm, tolls on caravans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxationForm Context triple: [Old Assyrian trade network, taxationForm, tolls on caravans]
-
A.
taxpayerBenefitForm
Indicates that there is a specific form documenting or enabling a benefit granted to a taxpayer.
-
B.
taxSchedule
Indicates the structured plan or timetable according to which taxes are calculated, applied, and/or collected.
-
C.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
D.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
-
E.
taxAuthority
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa1fe148190bf4e4f3f8c5adc47 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:57 a.m.