Triple
T38121078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vadu |
E951935
|
entity |
| Predicate | hasHistoricalMemory |
P145824
|
FINISHED |
| Object | resistance against Mughal Empire |
—
|
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: resistance against Mughal Empire | Statement: [Vadu, hasHistoricalMemory, resistance against Mughal Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalMemory Context triple: [Vadu, hasHistoricalMemory, resistance against Mughal Empire]
-
A.
retainsMemoriesOf
chosen
Indicates that one entity continues to hold or preserve memories about another entity or about events involving that entity.
-
B.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
C.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
D.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
E.
hasPriorHistory
Indicates that an entity has a previously recorded occurrence, condition, or involvement relevant to the current context.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: May 3, 2026, 4:21 p.m.