Triple
T24279271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurram |
E605493
|
entity |
| Predicate | taxCollectionRole |
P13245
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kurram, taxCollectionRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxCollectionRole Context triple: [Kurram, taxCollectionRole, yes]
-
A.
taxCollectorFor
Indicates that one entity is responsible for collecting taxes on behalf of another entity, such as a government, organization, or jurisdiction.
-
B.
taxAuthority
chosen
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
-
C.
taxCollectedFrom
Indicates that a tax payment is received by one party from another as the liable payer.
-
D.
taxpayerAction
Indicates an action performed by a taxpayer in relation to their tax obligations, such as filing, paying, reporting, or updating tax-related information.
-
E.
taxObligations
Indicates the duties or liabilities an entity has to pay taxes under applicable laws or regulations.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5032f48190a027e2d8b382ee79 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.