Triple
T5409407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Story of Bardoli |
E120974
|
entity |
| Predicate | documentsIssue |
P29535
|
FINISHED |
| Object | revenue assessment dispute |
—
|
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: revenue assessment dispute | Statement: [The Story of Bardoli, documentsIssue, revenue assessment dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsIssue Context triple: [The Story of Bardoli, documentsIssue, revenue assessment dispute]
-
A.
documentAtIssue
chosen
Indicates that a particular document is the specific item under consideration or dispute in a given context or proceeding.
-
B.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
C.
documentsCommunity
Indicates that an entity records, describes, or provides information about a particular community.
-
D.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
E.
documentsPeriod
Indicates that one entity documents, records, or provides written evidence about a specific time period associated with another entity.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8796a420819092c1771407cd1a5d |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.