Triple
T19575869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shailaputri |
E489856
|
entity |
| Predicate | positionInNavadurga |
P136329
|
FINISHED |
| Object | first form of Navadurga |
—
|
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: first form of Navadurga | Statement: [Shailaputri, positionInNavadurga, first form of Navadurga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInNavadurga Context triple: [Shailaputri, positionInNavadurga, first form of Navadurga]
-
A.
positionInBattle
Indicates the specific role or placement an entity occupies within the formation or structure of a battle.
-
B.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
C.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
D.
positionOnSecurity
Indicates the stance, opinion, or policy an entity holds regarding security-related issues or measures.
-
E.
positionWithinCastle
Indicates that one entity is located inside the spatial boundaries of a castle.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64024c5b08190bbff6df633857874 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:42 p.m.