Triple
T14532141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharaja of Jhansi |
E340940
|
entity |
| Predicate | taxObligations |
P114648
|
FINISHED |
| Object | tribute to British authorities |
—
|
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: tribute to British authorities | Statement: [Maharaja of Jhansi, taxObligations, tribute to British authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxObligations Context triple: [Maharaja of Jhansi, taxObligations, tribute to British authorities]
-
A.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
B.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
taxCollectorFor
Indicates that one entity is responsible for collecting taxes on behalf of another entity, such as a government, organization, or jurisdiction.
-
D.
taxPoint
Indicates the specific time or event at which a tax obligation is considered to arise or become chargeable for a transaction or activity.
-
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. 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea053f9bc8190901b9d321811d881 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:22 a.m.