Triple
T38694949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmadnagar Sultanate |
E949971
|
entity |
| Predicate | importantFort |
P191542
|
FINISHED |
| Object | Ahmadnagar Fort |
—
|
NE NERFINISHED |
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: Ahmadnagar Fort | Statement: [Ahmadnagar Sultanate, importantFort, Ahmadnagar Fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantFort Context triple: [Ahmadnagar Sultanate, importantFort, Ahmadnagar Fort]
-
A.
importantObject
Indicates that one entity is considered especially significant, central, or of high priority in relation to another entity or context.
-
B.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
C.
importantNote
Indicates that one entity is marked as an important or noteworthy note in relation to another entity.
-
D.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
E.
importantDOC
Indicates that the referenced document holds significant importance or priority within a given context or system.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.