Triple
T1105975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anandamath |
E25487
|
entity |
| Predicate | depictsConflictBetween |
P9742
|
FINISHED |
| Object | Indian ascetics |
—
|
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: Indian ascetics | Statement: [Anandamath, depictsConflictBetween, Indian ascetics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsConflictBetween Context triple: [Anandamath, depictsConflictBetween, Indian ascetics]
-
A.
depictsConflict
chosen
Indicates that one entity visually represents or portrays a situation of conflict involving another entity or entities.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
D.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
E.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e339f88190afc027216e95d2f7 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.